summaryrefslogtreecommitdiff
path: root/src/security/lockdown/Kconfig
diff options
context:
space:
mode:
authorDaniel Gröber <dxld@darkboxed.org>2020-05-26 22:21:41 +0200
committerPatrick Georgi <pgeorgi@google.com>2020-06-22 12:27:18 +0000
commita890138968894db60e022e846e5ee0a9fefde010 (patch)
treee66f96cb230f88a4842fdd328dab7b3e9b8f70df /src/security/lockdown/Kconfig
parent16dbbeb8959a07bbe873aac13579d65129c0ee0d (diff)
lockdown: Add hint for how to check for lockdown support in boot log
Change-Id: Iaceb2e82f900e52efcce702486e18d0483665640 Signed-off-by: Daniel Gröber <dxld@darkboxed.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/41749 Reviewed-by: Patrick Rudolph <siro@das-labor.org> Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/security/lockdown/Kconfig')
-rw-r--r--src/security/lockdown/Kconfig3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/security/lockdown/Kconfig b/src/security/lockdown/Kconfig
index 97094ff2e7..9d83a45b1d 100644
--- a/src/security/lockdown/Kconfig
+++ b/src/security/lockdown/Kconfig
@@ -18,7 +18,8 @@ config BOOTMEDIA_LOCK_CHIP
bool "Lock boot media using the chip"
help
Select this if you want the chip to lock specific regions.
- This only works on some chips, please check the code or boot log.
+ This only works on some chips, please check the code or search the
+ boot log for "BM-LOCKDOWN".
endchoice