On Tue, Oct 10, 2017 at 6:28 PM, Heinrich Schuchardt <xypron.g...@gmx.de> wrote: > On 10/10/2017 02:23 PM, Rob Clark wrote: >> >> These devices have small image size limits, so exclude EFI_LOADER to >> help avoid exceeding limits. >> >> Signed-off-by: Rob Clark <robdcl...@gmail.com> >> --- >> lib/efi_loader/Kconfig | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/lib/efi_loader/Kconfig b/lib/efi_loader/Kconfig >> index d2b6327119..6e22940da5 100644 >> --- a/lib/efi_loader/Kconfig >> +++ b/lib/efi_loader/Kconfig >> @@ -1,6 +1,6 @@ >> config EFI_LOADER >> bool "Support running EFI Applications in U-Boot" >> - depends on (ARM || X86) && OF_LIBFDT >> + depends on (ARM || X86) && OF_LIBFDT && !TARGET_OPENRD >> default y >> help >> Select this option if you want to run EFI applications (like >> grub2) >> > > I understand that with the progress we make on EFI implementation and other > parts of U-Boot the U-Boot image size is growing too big for direct loading > by the primary boot loader. > > The OPENRD boards have abundant memory, e.g. openrd_ultimate_defconfig > refers to a board with 512 MB RAM. > > So I think completely disabling EFI is not the solution. > Instead building an SPL should be enabled for this architecture when the > image is becoming too big for direct load. > > I am copying in the KIRKWOOD maintainers go get their view. >
I'm defn open to alternatives.. I don't know too much about what the limit was on these boards, other than we were close to it before, and the additional uefi proto's add <4k to the image size, which was enough to push it over the limit. Since this was effecting only a few boards, I went with this.. if it is only a temporary fix that can be removed soon, or if someone can do something better with a separate SPL build in the near term, that would be great. BR, -R _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot