summaryrefslogtreecommitdiff
path: root/cmd
diff options
context:
space:
mode:
authorHeinrich Schuchardt <xypron.glpk@gmx.de>2018-12-30 10:11:14 +0100
committerAlexander Graf <agraf@suse.de>2019-02-13 09:40:05 +0100
commit0ea8741ff65e2b1cf86763b1f6392499df286ce1 (patch)
tree74591b86acd2d338aa58f46438c1248da9aefdbe /cmd
parent0a76ba65568435e3cf630e146c4a630e9ee8db1f (diff)
downloadu-boot-0ea8741ff65e2b1cf86763b1f6392499df286ce1.tar.gz
u-boot-0ea8741ff65e2b1cf86763b1f6392499df286ce1.tar.bz2
u-boot-0ea8741ff65e2b1cf86763b1f6392499df286ce1.zip
efi_loader: CMD_BOOTEFI_HELLO_COMPILE in configs
It should not be necessary to adjust CMD_BOOTEFI_HELLO_COMPILE in config files. arch/arm/lib/crt0_arm_efi.S cannot be compiled in thumbs mode. We can disable CMD_BOOTEFI_HELLO_COMPILE for CONFIG_CPU_V7M. So there is no longer a need to disable it in stm32 configs. helloworld.efi can be built without problems on x86_64. So there is no need to disable it in chromebook_link64_defconfig and qemu-x86_64_defconfig. Same is true for ARM V7A. So do not disable CMD_BOOTEFI_HELLO_COMPILE in kp_imx6q_tpc_defconfig. Some architecture checks are already make for EFI_LOADER. There is no need to repeat them for CMD_BOOTEFI_HELLO_COMPILE Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Patrice.Chotard@st.com Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'cmd')
-rw-r--r--cmd/Kconfig2
1 files changed, 1 insertions, 1 deletions
diff --git a/cmd/Kconfig b/cmd/Kconfig
index ea1a325eb3..3ea42e4256 100644
--- a/cmd/Kconfig
+++ b/cmd/Kconfig
@@ -226,7 +226,7 @@ config CMD_BOOTEFI
config CMD_BOOTEFI_HELLO_COMPILE
bool "Compile a standard EFI hello world binary for testing"
- depends on CMD_BOOTEFI && (ARM || X86 || RISCV)
+ depends on CMD_BOOTEFI && !CPU_V7M && !SANDBOX
default y
help
This compiles a standard EFI hello world application with U-Boot so