Hi Takahiro,
2021年4月14日(水) 13:48 Takahiro Akashi takahiro.akashi@linaro.org:
So why not define UEFI load options (BOOTxxxx) and use UEFI boot manager ("bootefi bootmgr")? That is the way how UEFI (at least boot manager) boots the kernel.
Good point! Actually, I'm not sure how to define the BOOTxxxx in config.h (I only know how to include efivars file when build). Could you tell me how to do it? I would like to rewrite the default boot commands.
For example, => efidebug boot add 1 USBBOOT usb 0:1 /EFI/BOOT/bootaa64.efi <boot args> => efidebug boot add 2 MMCBOOT mmc 0:1 /EFI/BOOT/bootaa64.efi <boot args> => efidebug boot order 1 2 => bootefi bootmgr
Hmm, but this can not be embedded in the build process, can this?
Since "BOOTxxx" are non-volatile variables, we don't have to set them again once those commands are run.
What is the default behavior of "bootefi bootmgr" if there is no BOOTxxxx is set? If it just do nothing and exit, I think I can add it to the top of CONFIG_BOOTCOMMAND so that U-Boot can try it first. (BOOTxxxx will be set by user after boot)
But distro_bootcmd can also detect and try to boot "bootaa64.efi" anyway. (I'm not sure about the order of devices to detect though.)
Hmm, interesting. OK, I'll try to enable distro_bootcmd.
Thank you,
-Takahiro Akashi
Thank you,
-- Masami Hiramatsu