From: =?UTF-8?Q?Andr=c3=a9_Przywara?= Date: Mon, 2 Apr 2018 16:14:29 +0100 Subject: [U-Boot] [PATCH v4 00/19] sunxi: sync H3, H5, A64 DTs from mainline Linux In-Reply-To: <63321b82dcd75359@bloch.sibelius.xs4all.nl> References: <20180314015715.15615-1-andre.przywara@arm.com> <22104532-6ed7-d2cd-4292-9795525af3a5@arm.com> <63321b50bf3afff6@bloch.sibelius.xs4all.nl> <476777b5-edf2-8e80-6718-6f1d06cdcc49@arm.com> <63321b82dcd75359@bloch.sibelius.xs4all.nl> Message-ID: <9ae1cb46-04cb-e29d-a657-bc4f4ec86809@arm.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 02/04/18 13:47, Mark Kettenis wrote: Hi, >> From: =?UTF-8?Q?Andr=c3=a9_Przywara?= >> Date: Mon, 2 Apr 2018 12:51:50 +0100 >> >> On 02/04/18 12:20, Mark Kettenis wrote: >> >> .... >> >>>> This feature make U-Boot to have full Linux dts inside, Can't we >>>> implement automatic-boot-of-os distro to grab Linux dtb during >>>> commands stage like other distro does? Because this make few >>>> development struggles for U-Boot project like (few of the comments are >>>> repeated from previous mail, but I'm trying to group them all) >>>> - Unnecessary to maintain nodes which are not required for bootloader >>>> and which doesn't have proper dt drivers. >>>> - It becomes more patches for each-and-every sync. >>>> - We can compare the sync with Linux dt and simply apply on U-Boot >>>> which look not good to project growing. >>>> - Increase size(though it 10KB increase) it becomes unnecessary size >>>> from U-Boot point-of-view >>> >>> This is not just about booting Linux. And even if it was, it means >>> that you can only boot on hardware for which a full device tree is >>> included in your distro. So a new board that comes with a usable >>> U-Boot in SPI flash still won't work since the right device tree isn't >>> there. >> >> Ah right, I didn't even mention SPI flash in that thread. Thanks! >> >> Out of curiosity: what OS are you thinking about? Collecting trophies >> here ;-) I tried the FreeBSD-current installer the other day, and it >> worked pretty well. > > OpenBSD. ARMv8-wise, our support for Allwinner A64/H5 and Rockchip > RK3399 is pretty decent these days and Rockchip RK3328 is coming along > as well. Ah, great! I didn't know that OpenBSD was that far. Do you know of anything missing in the DT or UEFI support from mainline U-Boot? I put firmware images on my Pine64 github repo[1] for A64 and H5 boards, which are based on 2018.03 plus this series, if you want to give it a try. Trying to wrap my around INSTALL.arm64, but you might be faster ;-) Does 6.2 provide enough to work? Or shall I wait till the 15th? > And I'm working on Marvell 8040 support. There is support > for ARMv7 as well which includes many of the older Allwinner SoCs. > We don't have the resources to build images for all the different > boards that are out there though, which probably is the biggest > stumbling block for getting OpenBSD to run. Our bootloader is UEFI, That sounds good! > so with a recent enough U-Boot in flash the default install.fs image Is that the FFS filesystem in the OpenBSD partition of miniroot.fs? Which just contains the bsd.rd kernel + RAM fs? The 6.2 directory didn't have an explicit install.fs image. Cheers, Andre [1] https://github.com/apritzel/pine64/tree/master/images > should just work. It does on Rock64! Otherwise you have to know the > magic to write the U-Boot image at the right location into that image > to make it boot. > > Cheers, > > Mark >