summaryrefslogtreecommitdiff
path: root/src/vboot/Kconfig
diff options
context:
space:
mode:
authorJulius Werner <jwerner@chromium.org>2017-03-16 19:32:48 -0700
committerJulius Werner <jwerner@chromium.org>2017-03-28 22:14:43 +0200
commitfa8fa7dd540db7c6f363f75c12b2063c3cdc3908 (patch)
tree0a24818a502d543cdcfa3b1ab3b7062eb935fadc /src/vboot/Kconfig
parent94d9411415e624f70ba8451886e5b96a1f56b159 (diff)
vboot: Remove VBOOT_DYNAMIC_WORK_BUFFER Kconfig option
VBOOT_DYNAMIC_WORK_BUFFER and VBOOT_STARTS_IN_ROMSTAGE are equivalent in practice. We can't have a dynamic work buffer unless we start in/after romstage, and there'd be no reason to go with a static buffer if we do. Let's get rid of one extra option and merge the two. Change-Id: I3f953c8d2a8dcb3f65b07f548184d6dd0eb688fe Signed-off-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://review.coreboot.org/18979 Tested-by: build bot (Jenkins) Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Diffstat (limited to 'src/vboot/Kconfig')
-rw-r--r--src/vboot/Kconfig11
1 files changed, 0 insertions, 11 deletions
diff --git a/src/vboot/Kconfig b/src/vboot/Kconfig
index 2b6cde1c19..0c72d4775e 100644
--- a/src/vboot/Kconfig
+++ b/src/vboot/Kconfig
@@ -95,17 +95,6 @@ config RETURN_FROM_VERSTAGE
reused by the succeeding stage. This is useful if a RAM space is too
small to fit both the verstage and the succeeding stage.
-config VBOOT_DYNAMIC_WORK_BUFFER
- bool "Vboot's work buffer is dynamically allocated."
- default y if ARCH_ROMSTAGE_X86_32 && !SEPARATE_VERSTAGE
- default n
- depends on VBOOT
- help
- This option is used when there isn't enough pre-main memory
- RAM to allocate the vboot work buffer. That means vboot verification
- is after memory init and requires main memory to back the work
- buffer.
-
config VBOOT_SAVE_RECOVERY_REASON_ON_REBOOT
bool
default n