Hi Heinrich, On Sat, 3 May 2025 at 01:16, Heinrich Schuchardt <heinrich.schucha...@canonical.com> wrote: > > > > Simon Glass <s...@chromium.org> schrieb am Sa., 3. Mai 2025, 04:10: >> >> Hi Heinrich, >> >> On Fri, 2 May 2025 at 10:16, Heinrich Schuchardt >> <heinrich.schucha...@canonical.com> wrote: >> > >> > On 5/2/25 16:49, Simon Glass wrote: >> > > Hi Heinrich, >> > > >> > > On Mon, 21 Apr 2025 at 10:26, Heinrich Schuchardt >> > > <heinrich.schucha...@canonical.com> wrote: >> > >> >> > >> The boot method is deprecated as the EFI boot manager covers this >> > >> functionality. >> > >> >> > >> Signed-off-by: Heinrich Schuchardt <heinrich.schucha...@canonical.com> >> > >> --- >> > >> boot/Kconfig | 1 - >> > >> 1 file changed, 1 deletion(-) >> > >> >> > >> diff --git a/boot/Kconfig b/boot/Kconfig >> > >> index 71ddb37f6bb..b973d9eb0a7 100644 >> > >> --- a/boot/Kconfig >> > >> +++ b/boot/Kconfig >> > >> @@ -595,7 +595,6 @@ config BOOTMETH_EFILOADER >> > >> bool "Bootdev support for EFI boot" >> > >> depends on EFI_BINARY_EXEC >> > >> imply CMD_TFTPBOOT if CMD_NET >> > >> - default y >> > >> help >> > >> This bootmeth is obsolete. BOOTMETH_EFI_BOOTMGR takes care of >> > >> launching EFI\BOOT\BOOT<ARCH>.EFI if not boot option matches. >> > >> -- >> > >> 2.48.1 >> > >> >> > > >> > > As mentioned on the other patch, we need to keep this enabled and it >> > > isn't obsolete. >> > > >> > > Regards, >> > > Simon >> > >> > Please, read the UEFI specification especially chapter 3 "Boot Manager". >> > >> > * The functionality is fully covered by the boot manager. >> > * The current implementation of the method does not comply with the UEFI >> > specification. Especially if run before the boot manager. >> >> We're going to have to go through this together sometime as it seems >> like chicken & egg to me. We don't want Boot Manager first because it >> is slow and stuffs up FEL on sunxi etc., we don't want it last because >> then it has to wait for networking, we don't know whether bootmgr is >> being used or not, so we just have to put it in the middle, but then >> we don't know whether it will succeed, at which point we have to go >> back and try the whole boot again..? > > > Sure there can be a situation where none of the boot methods will succeed. > E.g. if there are no boot media. This has been the case before the series and > won't be different with the series. > > But if we reach the boot manager after trying FEL, extlinux, script and none > of these booted retrying these would not make any sense as they would fail > again. > > The boot manager already comprises booting via EFI/BOOT/BOOT<ARCH>.EFI. And > this must not be tried before booting according to BootNext and BootOrder. So > we can safely delete that non-compliant bootmeth_efi.
OK let's discuss this and see what we can figure out. Perhaps we could come up with an env var which controls this, or similar. Regards, SImon
