summaryrefslogtreecommitdiff
path: root/src/security
diff options
context:
space:
mode:
authorYu-Ping Wu <yupingso@google.com>2020-02-14 17:16:53 +0800
committerPatrick Georgi <pgeorgi@google.com>2020-02-18 14:58:52 +0000
commit214fb9b511faaa59716a1b65a43438781f6237ef (patch)
tree0f01eb477daa69ddfe134b2568f6c29ab0a4678a /src/security
parentd346a19dedf28aecc4a2bce7ab9ee08323b63a1c (diff)
downloadcoreboot-214fb9b511faaa59716a1b65a43438781f6237ef.tar.xz
security/vboot: Correct help text of VBOOT_STARTS_IN_ROMSTAGE
Since CB:37231 [1], the vboot working data has been replaced with vboot work buffer, so corrrect the help text of option VBOOT_STARTS_IN_ROMSTAGE accordingly. [1] security/vboot: Remove struct vboot_working_data BRANCH=none BUG=chromium:1021452 TEST=none Change-Id: I80783274179ae7582bbb4c8f9d392895623badce Signed-off-by: Yu-Ping Wu <yupingso@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/38900 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Joel Kitching <kitching@google.com>
Diffstat (limited to 'src/security')
-rw-r--r--src/security/vboot/Kconfig4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/security/vboot/Kconfig b/src/security/vboot/Kconfig
index 28639529bb..e366cc4c09 100644
--- a/src/security/vboot/Kconfig
+++ b/src/security/vboot/Kconfig
@@ -114,8 +114,8 @@ config VBOOT_STARTS_IN_ROMSTAGE
depends on !VBOOT_STARTS_IN_BOOTBLOCK
help
Firmware verification happens during the end of romstage (after
- memory initialization). This implies that vboot working data is
- allocated in CBMEM.
+ memory initialization). This implies that the vboot work buffer is
+ in CBMEM from the start and doesn't need to be reserved in memlayout.
config VBOOT_MOCK_SECDATA
bool "Mock secdata for firmware verification"