diff options
| author | Simon Glass | 2022-04-24 23:31:17 -0600 |
|---|---|---|
| committer | Tom Rini | 2022-04-25 10:00:04 -0400 |
| commit | acfa9bdfa7391f1872aa67bc6e4d3cd38e11d6c9 (patch) | |
| tree | 1625d6aea62d52abe5db68742605200745891b20 /boot/Kconfig | |
| parent | dab2c2859b68ad04f276555812ecfbb25680cc61 (diff) | |
bootstd: Add an implementation of EFI boot
Add a bootmeth driver which handles EFI boot, using EFI_LOADER.
In effect, this provides the same functionality as the 'bootefi' command
and shares the same code. But the interface into it is via a bootmeth,
so it does not require any special scripts, etc.
For now this requires the 'bootefi' command be enabled. Future work may
tidy this up so that it can be used without CONFIG_CMDLINE being enabled.
There was much discussion about whether this is needed, but it seems
that it is, at least for now.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'boot/Kconfig')
| -rw-r--r-- | boot/Kconfig | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/boot/Kconfig b/boot/Kconfig index 9e02a7549af..0bfea2791da 100644 --- a/boot/Kconfig +++ b/boot/Kconfig @@ -349,6 +349,27 @@ config BOOTMETH_DISTRO_PXE This provides a way to try out standard boot on an existing boot flow. +config BOOTMETH_EFILOADER + bool "Bootdev support for EFI boot" + depends on CMD_BOOTEFI + default y + help + Enables support for EFI boot using bootdevs. This makes the + bootdevs look for a 'boot<arch>.efi' on each filesystem + they scan. The resulting file is booted after enabling U-Boot's + EFI loader support. + + The <arch> depends on the architecture of the board: + + aa64 - aarch64 (ARM 64-bit) + arm - ARM 32-bit + ia32 - x86 32-bit + x64 - x86 64-bit + riscv32 - RISC-V 32-bit + riscv64 - RISC-V 64-bit + + This provides a way to try out standard boot on an existing boot flow. + endif config LEGACY_IMAGE_FORMAT |