aboutsummaryrefslogtreecommitdiff
path: root/doc/README.u-boot_on_efi
diff options
context:
space:
mode:
authorBin Meng2018-06-12 08:36:18 -0700
committerBin Meng2018-06-17 21:16:04 +0800
commit32151d40172870e7772b1a393935001979a01aea (patch)
tree36f7e81b7d5a750f7452c8a85575e46942dfa5c6 /doc/README.u-boot_on_efi
parent3773c6a20a1cd736a340f1141a6d3d8ee3c2ddc6 (diff)
x86: Add generic EFI payload support
It is possible to create a generic EFI payload for all x86 boards. The payload is configured to include as many generic drivers as possible. All stuff that touches low-level initialization are not allowed as such is the EFI BIOS's responsibility. Platform specific drivers (like gpio, spi, etc) are not included. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc/README.u-boot_on_efi')
-rw-r--r--doc/README.u-boot_on_efi19
1 files changed, 9 insertions, 10 deletions
diff --git a/doc/README.u-boot_on_efi b/doc/README.u-boot_on_efi
index 0349c5663af..8fba112e116 100644
--- a/doc/README.u-boot_on_efi
+++ b/doc/README.u-boot_on_efi
@@ -71,12 +71,13 @@ Just build U-Boot as normal, e.g.
make efi-x86_defconfig
make
-To build U-Boot as an EFI payload (32-bit or 64-bit EFI can be used), adjust an
-existing config (like qemu-x86_defconfig) to enable CONFIG_EFI, CONFIG_EFI_STUB
-and either CONFIG_EFI_STUB_32BIT or CONFIG_EFI_STUB_64BIT. All of these are
-boolean Kconfig options. Then build U-Boot as normal, e.g.
+To build U-Boot as an EFI payload (32-bit or 64-bit EFI can be used), enable
+CONFIG_EFI, CONFIG_EFI_STUB, and select either CONFIG_EFI_STUB_32BIT or
+CONFIG_EFI_STUB_64BIT. The efi-x86_payload configs (efi-x86_payload32_defconfig
+and efi-x86_payload32_defconfig) are set up for this. Then build U-Boot as
+normal, e.g.
- make qemu-x86_defconfig
+ make efi-x86_payload32_defconfig (or efi-x86_payload64_defconfig)
make
You will end up with one of these files depending on what you build for:
@@ -211,11 +212,6 @@ Future work
-----------
This work could be extended in a number of ways:
-- Add a generic x86 EFI payload configuration. At present you need to modify
-an existing one, but mostly the low-level x86 code is disabled when booting
-on EFI anyway, so a generic 'EFI' board could be created with a suitable set
-of drivers enabled.
-
- Add ARM support
- Add 64-bit application support
@@ -241,6 +237,9 @@ arch/x86/cpu/efi
board/efi/efi-x86/efi.c
x86 board code for running as an EFI application
+board/efi/efi-x86_payload
+ generic x86 EFI payload board support code
+
common/cmd_efi.c
the 'efi' command