diff options
| author | Bill Richardson <wfrichar@chromium.org> | 2012-08-28 15:00:51 -0700 |
|---|---|---|
| committer | Gerrit <chrome-bot@google.com> | 2012-08-28 16:39:33 -0700 |
| commit | 9dc62178c97b94e5c308f1c36fd0858c316959e5 (patch) | |
| tree | cbf17a7f91bd3f53db1a6b7ef08e3381ef1f6c88 /utility | |
| parent | 1d053f6e2341dae1b2c48a422fbb5ce46a3bbefc (diff) | |
| download | vboot-9dc62178c97b94e5c308f1c36fd0858c316959e5.tar.gz | |
Add VB_INIT_FLAG_SW_WP_ENABLED to VbInit() input flags.
We need to know not only whether the HW WP pin is asserted, but whether the
flash chip has configured its software protection registers to actually
protect anything. This flag can be used to indicate that.
BUG=chrome-os-partner:13265
BRANCH=link
TEST=none
This just adds the flag. Nothing actually sets the flag yet, so there's
nothing to test.
Change-Id: Icba9945fb56eb3a4681486c630cbbdc9232485ef
Signed-off-by: Bill Richardson <wfrichar@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31642
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'utility')
| -rw-r--r-- | utility/crossystem_main.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/utility/crossystem_main.c b/utility/crossystem_main.c index 1b926655..7528f019 100644 --- a/utility/crossystem_main.c +++ b/utility/crossystem_main.c @@ -70,6 +70,8 @@ const Param sys_param_list[] = { {"ro_fwid", IS_STRING, "Read-only firmware ID"}, {"savedmem_base", 0, "RAM debug data area physical address", "0x%08x"}, {"savedmem_size", 0, "RAM debug data area size in bytes"}, + {"sw_wpsw_boot", 0, + "Firmware write protect software setting enabled at boot"}, {"tpm_fwver", 0, "Firmware version stored in TPM", "0x%08x"}, {"tpm_kernver", 0, "Kernel version stored in TPM", "0x%08x"}, {"tried_fwb", 0, "Tried firmware B before A this boot"}, |