summaryrefslogtreecommitdiff
path: root/src/soc/marvell/bg4cd
diff options
context:
space:
mode:
authorAaron Durbin <adurbin@chromium.org>2015-04-28 16:17:25 -0500
committerPatrick Georgi <pgeorgi@google.com>2015-04-30 13:05:36 +0200
commit57e37287f45cc4911accbea21cc9a9ac0f0adde7 (patch)
tree4cf10cacee028cfce7b32d369a8ceed01b8da83e /src/soc/marvell/bg4cd
parent5abcba71212bf162661b22aec7f8ad7141547668 (diff)
downloadcoreboot-57e37287f45cc4911accbea21cc9a9ac0f0adde7.tar.xz
vboot: add and rejuggle Kconfig options
The ChromeOS machines employing vboot verfication require different combinations of support: 1. When vboot verification starts. 2. Is the vboot code a separate stage or program? 3. If a separate stage, does the that vboot program (verstage) return to the stage that loaded the verstage? For the above, #1 is dependent on when to load/run vboot logic which is orthogonal to #2. However, #3 is dependent on #2. The logic to act on the combinations follows in subsequent patches. Change-Id: I39ef7a7c2858e7de43aa99c38121e85a57f1f2f6 Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: http://review.coreboot.org/10024 Tested-by: build bot (Jenkins) Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Diffstat (limited to 'src/soc/marvell/bg4cd')
-rw-r--r--src/soc/marvell/bg4cd/Kconfig2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/soc/marvell/bg4cd/Kconfig b/src/soc/marvell/bg4cd/Kconfig
index 96fd8efe77..9c0dc140f7 100644
--- a/src/soc/marvell/bg4cd/Kconfig
+++ b/src/soc/marvell/bg4cd/Kconfig
@@ -32,7 +32,7 @@ config SOC_MARVELL_BG4CD
select GENERIC_UDELAY
select HAVE_MONOTONIC_TIMER
select GENERIC_GPIO_LIB
- select VERSTAGE_IN_BOOTBLOCK
+ select VBOOT_STARTS_IN_BOOTBLOCK
if SOC_MARVELL_BG4CD