fastboot: set NV storage directly instead of VbLockDevice()
All VbLockDevice() does is the equivalent of
vbnv_write(VB2_NV_DISABLE_DEV_REQUEST, 1);
So, do that, rather than requiring another API. Fastboot already uses
vbnv_write() in other places.
This will allow removing the VbLockDevice() API entirely, rather than
needing to rewrite it to support larger NV storage records.
BUG=chromium:789276
BRANCH=none
TEST=none (no firmware in ToT uses fastboot)
Change-Id: I915a7384d9a736574ca2e44649064fb61b8ce638
Signed-off-by: Randall Spangler <rspangler@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/944183
Reviewed-by: Furquan Shaikh <furquan@chromium.org>
1 file changed
