efi_selftest: enable CONFIG_CMD_BOOTEFI_SELFTEST
authorHeinrich Schuchardt <xypron.glpk@gmx.de>
Wed, 20 Sep 2017 19:14:37 +0000 (21:14 +0200)
committerAlexander Graf <agraf@suse.de>
Thu, 5 Oct 2017 12:47:02 +0000 (14:47 +0200)
The EFI selftest has been broken by a patch on efi-next.
We should enable CONFIG_CMD_BOOTEFI_SELFTEST on
qemu-x86_defconfig and qemu-x86_64_defconfig by default
to catch this type of problem in the Travis CI tests.

These systems typically have abundant memory so that
enabling this option should not pose a problem.

Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>
Signed-off-by: Alexander Graf <agraf@suse.de>
configs/qemu-x86_64_defconfig
configs/qemu-x86_defconfig

index 67e9a45..c12d530 100644 (file)
@@ -64,3 +64,4 @@ CONFIG_USB_KEYBOARD=y
 CONFIG_FRAMEBUFFER_SET_VESA_MODE=y
 CONFIG_FRAMEBUFFER_VESA_MODE_111=y
 CONFIG_CONSOLE_SCROLL_LINES=5
+CONFIG_CMD_BOOTEFI_SELFTEST=y
index 7ce97ff..d84e1d7 100644 (file)
@@ -44,3 +44,4 @@ CONFIG_USB_KEYBOARD=y
 CONFIG_FRAMEBUFFER_SET_VESA_MODE=y
 CONFIG_FRAMEBUFFER_VESA_MODE_111=y
 CONFIG_CONSOLE_SCROLL_LINES=5
+CONFIG_CMD_BOOTEFI_SELFTEST=y