On Fri, Mar 31, 2023 at 10:25:56AM +1300, Simon Glass wrote: > The current EFI implementation has a strange quirk where it watches > loaded files and uses the last-loaded file to determine the device that > is being booted from. > > This is confusing with bootstd, where multiple options may exist. Even > loading a device tree will cause it to go wrong. There is no API for > passing this information, since the only entry into booting an EFI image > is the 'bootefi' command. > > To work around this, call efi_set_bootdev() for EFI images, if possible, > just before booting. > > Signed-off-by: Simon Glass <s...@chromium.org>
Shouldn't this all be a simple wrapper around the EFI Standard BootDeviceOrder or whatever that's called? -- Tom
signature.asc
Description: PGP signature
