On Fri, Mar 04, 2022 at 04:30:11PM +0000, Andre Przywara wrote: > The FVP base model is relying on a DT for Linux operation, so there is > no reason we would need to rely on hardcoded information for U-Boot. > Letting U-Boot use a DT will open up the usage of actual peripherals, > beyond the support for semihosting only. > > Enable OF_CONTROL in the Kconfig, and use the latest dts files from > Linux. Depending on whether we use the boot-wrapper or TF-A, there is > already a DTB provided or not, respectively. > > To cover the boot-wrapper, we add an arm64 Linux kernel header, which > allows the boot-wrapper to treat U-Boot like a Linux kernel. U-Boot will > find the pointer to the DTB in x0, and will use it. > > Even though TF-A carries a DT, at the moment this is not made available > to non-secure world, so to not break users, we use the U-Boot provided > DTB copy in that case. For some reason TF-A puts some DT like structure > at the address x0 is pointing at, but that is very small and doesn't > carry any hardware information. Make the code to ignore those small DTBs. > > Signed-off-by: Andre Przywara <andre.przyw...@arm.com> > --- > arch/arm/Kconfig | 2 ++ > arch/arm/dts/Makefile | 1 +
> board/armltd/vexpress64/Kconfig | 8 ++++++-- > board/armltd/vexpress64/vexpress64.c | 8 +++++++- > configs/vexpress_aemv8a_semi_defconfig | 2 +- > 5 files changed, 17 insertions(+), 4 deletions(-) > > diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig > index 34dbd73cce..afb42e62d8 100644 Applied to u-boot/next, thanks! -- Tom
signature.asc
Description: PGP signature
