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 /tests | |
| 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 'tests')
| -rw-r--r-- | tests/vboot_api_init_tests.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/tests/vboot_api_init_tests.c b/tests/vboot_api_init_tests.c index 3816e075..c10e7d08 100644 --- a/tests/vboot_api_init_tests.c +++ b/tests/vboot_api_init_tests.c @@ -144,6 +144,12 @@ static void VbInitTest(void) { TEST_EQ(shared->flags, VBSD_BOOT_FIRMWARE_WP_ENABLED, " shared flags WP"); ResetMocks(); + iparams.flags = VB_INIT_FLAG_SW_WP_ENABLED; + TestVbInit(0, 0, "Flags test SW WP"); + TEST_EQ(shared->flags, VBSD_BOOT_FIRMWARE_SW_WP_ENABLED, + " shared flags SW WP"); + + ResetMocks(); iparams.flags = VB_INIT_FLAG_RO_NORMAL_SUPPORT; TestVbInit(0, 0, " flags test RO normal"); TEST_EQ(shared->flags, VBSD_BOOT_RO_NORMAL_SUPPORT, |