[PATCH v2 48/71] bootstd: Support reading the device tree with EFI
sjg at chromium.org
Fri Jan 13 19:00:29 CET 2023
On Sun, 8 Jan 2023 at 03:25, Mark Kettenis <mark.kettenis at xs4all.nl> wrote:
> > From: Simon Glass <sjg at chromium.org>
> > Date: Sat, 7 Jan 2023 19:50:24 -0700
> > With EFI booting the device tree is required but is not actually specified
> > in any way. The normal method is to use a fdtfile environment variable to
> > get the filename, then look for that file on the media.
> > Implement this in the bootmeth.
> > Signed-off-by: Simon Glass <sjg at chromium.org>
> > ---
> Hi Simon,
> The distroboot scripts also reads dtb files from the root directory of
> the ESP (so without the "dtb/" prefix). This code needs to do that as
> well otherwise some folks will run with a different device tree after
> switching to bootstd.
> The construction of a fallback dtb filename based on soc, board and
> boardver is only done for (32-bit) arm and not for arm64. It isn't
> done for riscv either. That feels to me like someone recognized that
> was a bit of a mistake and shouldn't be done for modern targets. So I
> think that code should be under the same
> #if defined(CONFIG_ARM) && !defined(CONFIG_ARM64)
> as it is now in config_distro_bootcmd.h.
OK, thanks for that. Yes I deliberately dropped that in the hope that
we can have one standard.
I will send a patch to add that.
More information about the U-Boot-Custodians