summaryrefslogtreecommitdiff
path: root/doc/develop
diff options
context:
space:
mode:
authorSimon Glass <[email protected]>2025-05-28 10:03:16 -0600
committerHeinrich Schuchardt <[email protected]>2025-07-26 07:34:31 +0200
commit81ce639e61c990e4d3b88cc975bf552e8b509090 (patch)
treeadb90125802c29a1a57da82378ca2f2fb741e513 /doc/develop
parent0029f2447bd4fac23d0ec6107c0b911c50c2c334 (diff)
efi: Create a new CONFIG_EFI
Create a Kconfig which indicates that EFI functionality is in use, either as a client (EFI app / stub) or provider (EFI loader). This will make it easier to share code between these two parts of U-Boot Signed-off-by: Simon Glass <[email protected]>
Diffstat (limited to 'doc/develop')
-rw-r--r--doc/develop/uefi/u-boot_on_efi.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/develop/uefi/u-boot_on_efi.rst b/doc/develop/uefi/u-boot_on_efi.rst
index 9068894e408..177e887ebd9 100644
--- a/doc/develop/uefi/u-boot_on_efi.rst
+++ b/doc/develop/uefi/u-boot_on_efi.rst
@@ -45,9 +45,9 @@ First choose a board that has EFI support and obtain an EFI implementation
for that board. It will be either 32-bit or 64-bit. Alternatively, you can
opt for using QEMU [1] and the OVMF [2], as detailed below.
-To build U-Boot as an EFI application, enable CONFIG_EFI_CLIENT and CONFIG_EFI_APP.
-The efi-x86_app32 and efi-x86_app64 configs are set up for this. Just build
-U-Boot as normal, e.g.::
+To build U-Boot as an EFI application, enable CONFIG_EFI_CLIENT and
+CONFIG_EFI_APP. The efi-x86_app32 and efi-x86_app64 configs are set up for
+this. Just build U-Boot as normal, e.g.::
make efi-x86_app32_defconfig
make