summaryrefslogtreecommitdiff
path: root/util/temp_metrics.conf
diff options
context:
space:
mode:
authorShawn Nematbakhsh <shawnn@chromium.org>2017-06-19 15:38:19 -0700
committerchrome-bot <chrome-bot@chromium.org>2017-06-27 21:28:05 -0700
commit75edd8984f360ec1f46906facb6e624404b6bc0e (patch)
tree5bd5863ecf39a03e3f0fb2cfa076fb5e80f80b8c /util/temp_metrics.conf
parentf534936ca5435e3b31fd2e31acc4ae9d47d57b5d (diff)
downloadchrome-ec-75edd8984f360ec1f46906facb6e624404b6bc0e.tar.gz
vboot_hash: Don't auto-start hashing in recovery mode
If we have requested the host to go to recovery mode, the host will usually not need an RW hash because it won't do EC SW sync. Therefore, do not auto-start calculation of our hash if we've requested recovery. This may avoid past recovery-breaking bugs due to unexpected RW contents. If the host does need the hash after all, it will manually request that the computation start. BUG=chromium:612966 BRANCH=None TEST=Boot to recovery mode on kevin, verify that "hash start" print is not seen on UART. Signed-off-by: Shawn Nematbakhsh <shawnn@chromium.org> Change-Id: I66d2d74398357dfe30e39882feec8cfba4cc945c Reviewed-on: https://chromium-review.googlesource.com/540695 Commit-Ready: Shawn N <shawnn@chromium.org> Tested-by: Shawn N <shawnn@chromium.org> Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'util/temp_metrics.conf')
0 files changed, 0 insertions, 0 deletions