diff options
| author | Bill Richardson <wfrichar@chromium.org> | 2012-06-07 02:20:20 -0700 |
|---|---|---|
| committer | Gerrit <chrome-bot@google.com> | 2012-06-07 14:33:29 -0700 |
| commit | 94ff216f3250ebccd3196423d427c1c9a552590b (patch) | |
| tree | feac1995c7134fad16b8178af9e0e083f83210f5 /util | |
| parent | 8fcfec5f7f80d521aad34b6b503455de2b84bbc2 (diff) | |
| download | chrome-ec-94ff216f3250ebccd3196423d427c1c9a552590b.tar.gz | |
Don't echo the NV recovery requests back to the BIOS. It knows.
When recovery is required, it will be because there's either a hardware pin
pulled somewhere, or because the recovery_reason is set in NVRAM. Coreboot
and U-Boot can see both of those, so the EC shouldn't make up a new reason.
If it does, it changes the original cause.
BUG=chrome-os-partner:9706
TEST=manual
Reset the EC using ESC+Power (Refresh+Power on EVT). At a root shell, run
crossystem recovery_request=11
reboot
When you see the Recovery screen, press TAB. It should say
recovery_reason: 0x0b We have no idea what this means
Prior to this fix, you'd see recovery_reason 2 instead, which is wrong.
Change-Id: Ie54185471927e7e829962d30bba9d142d593088f
Signed-off-by: Bill Richardson <wfrichar@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/24152
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'util')
0 files changed, 0 insertions, 0 deletions