x86: Rename efi-x86 target to efi-x86_app

To avoid confusion, let's rename the efi-x86 target to efi-x86_app.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
lime2-spi
Bin Meng 7 years ago
parent d441ec8298
commit 3ebd892fda
  1. 2
      arch/x86/cpu/efi/Makefile
  2. 0
      arch/x86/cpu/efi/app.c
  3. 2
      arch/x86/cpu/intel_common/Makefile
  4. 2
      arch/x86/dts/Makefile
  5. 4
      arch/x86/dts/efi-x86_app.dts
  6. 6
      board/efi/Kconfig
  7. 6
      board/efi/efi-x86_app/Kconfig
  8. 0
      board/efi/efi-x86_app/MAINTAINERS
  9. 2
      board/efi/efi-x86_app/Makefile
  10. 0
      board/efi/efi-x86_app/app.c
  11. 4
      configs/efi-x86_app_defconfig
  12. 8
      doc/README.u-boot_on_efi
  13. 0
      include/configs/efi-x86_app.h

@ -3,7 +3,7 @@
# Copyright (c) 2015 Google, Inc
ifdef CONFIG_EFI_APP
obj-y += efi.o
obj-y += app.o
obj-y += sdram.o
endif

@ -10,7 +10,7 @@ obj-$(CONFIG_$(SPL_)X86_32BIT_INIT) += mrc.o
endif
obj-y += cpu.o
obj-y += lpc.o
ifndef CONFIG_TARGET_EFI
ifndef CONFIG_TARGET_EFI_APP
obj-y += microcode.o
endif
obj-y += pch.o

@ -10,7 +10,7 @@ dtb-y += bayleybay.dtb \
crownbay.dtb \
dfi-bt700-q7x-151.dtb \
edison.dtb \
efi.dtb \
efi-x86_app.dtb \
efi-x86_payload.dtb \
galileo.dtb \
minnowmax.dtb \

@ -9,8 +9,8 @@
/include/ "tsc_timer.dtsi"
/ {
model = "EFI";
compatible = "efi,app";
model = "EFI x86 Application";
compatible = "efi,x86-app";
chosen {
stdout-path = &serial;

@ -4,8 +4,8 @@ choice
prompt "Mainboard model"
optional
config TARGET_EFI
bool "efi"
config TARGET_EFI_APP
bool "efi application"
help
This target is used for running U-Boot on top of EFI. In
this case EFI does the early initialisation, and U-Boot
@ -22,7 +22,7 @@ config TARGET_EFI_PAYLOAD
endchoice
source "board/efi/efi-x86/Kconfig"
source "board/efi/efi-x86_app/Kconfig"
source "board/efi/efi-x86_payload/Kconfig"
endif

@ -1,7 +1,7 @@
if TARGET_EFI
if TARGET_EFI_APP
config SYS_BOARD
default "efi-x86"
default "efi-x86_app"
config SYS_VENDOR
default "efi"
@ -10,6 +10,6 @@ config SYS_SOC
default "efi"
config SYS_CONFIG_NAME
default "efi-x86"
default "efi-x86_app"
endif

@ -2,4 +2,4 @@
#
# Copyright (c) 2015 Google, Inc
obj-y += efi.o
obj-y += app.o

@ -2,8 +2,8 @@ CONFIG_X86=y
CONFIG_DEBUG_UART_BASE=0
CONFIG_DEBUG_UART_CLOCK=0
CONFIG_VENDOR_EFI=y
CONFIG_DEFAULT_DEVICE_TREE="efi"
CONFIG_TARGET_EFI=y
CONFIG_DEFAULT_DEVICE_TREE="efi-x86_app"
CONFIG_TARGET_EFI_APP=y
CONFIG_DEBUG_UART=y
CONFIG_FIT=y
CONFIG_USE_BOOTARGS=y

@ -65,10 +65,10 @@ 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 (32-bit EFI required), enable CONFIG_EFI
and CONFIG_EFI_APP. The efi-x86 config (efi-x86_defconfig) is set up for this.
Just build U-Boot as normal, e.g.
and CONFIG_EFI_APP. The efi-x86_app config (efi-x86_app_defconfig) is set up
for this. Just build U-Boot as normal, e.g.
make efi-x86_defconfig
make efi-x86_app_defconfig
make
To build U-Boot as an EFI payload (32-bit or 64-bit EFI can be used), enable
@ -234,7 +234,7 @@ lib/efi
arch/x86/cpu/efi
x86 support code for running as an EFI application and payload
board/efi/efi-x86/efi.c
board/efi/efi-x86_app/efi.c
x86 board code for running as an EFI application
board/efi/efi-x86_payload

Loading…
Cancel
Save