diff options
author | Julius Werner <jwerner@chromium.org> | 2017-07-17 13:51:25 -0700 |
---|---|---|
committer | chrome-bot <chrome-bot@chromium.org> | 2017-07-18 02:36:16 -0700 |
commit | 8b71425257d251858410de71efcf389df8b200d2 (patch) | |
tree | 4f4e0e0d9d58a683a6e3db4ed06e5ca67123428d /firmware/lib/tpm2_lite/tlcl.c | |
parent | 2a7e9b84ac69c374112a13fd16fbf7cb996b78bf (diff) | |
download | vboot-8b71425257d251858410de71efcf389df8b200d2.tar.gz |
crossystem: Remove defunct sw_wpsw_boot fieldstabilize-9765.7.Bstabilize-9765.39.B
The sw_wpsw_boot field only ever worked correctly on some platforms. It
also isn't used anywhere in the codebase (only other reference is a
comment about how it doesn't always work in factory_installer.sh), and
it's no longer clear what it was meant for in the first place
(b/35510092 hints at needing it for some planned feature that was never
implemented). Let's get rid of it to avoid confusing people.
If userspace tools need to know the software write-protect state, they
can instead run flashrom directly. For feedback reports, this output is
already included in the "verified boot" section.
BRANCH=none
BUG=chromium:508269,chromium:742685
TEST=none
Change-Id: I8975b1e2c8e604b4cb48d092c13b923b4db2d207
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/575389
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'firmware/lib/tpm2_lite/tlcl.c')
0 files changed, 0 insertions, 0 deletions