summaryrefslogtreecommitdiff
path: root/action_processor.h
diff options
context:
space:
mode:
authorAndrew de los Reyes <adlr@chromium.org>2011-04-20 17:15:47 -0700
committerAndrew de los Reyes <adlr@chromium.org>2011-04-20 17:15:47 -0700
commitc1d5c93ddf56e193fd501e5f8fc3fc45efdc560f (patch)
treef328b488f08c1d9e639097dfc3ae04a176499a45 /action_processor.h
parente72f9c028fe41052cc18c95411fc1cd21d5029a3 (diff)
AU: Handle firmware update failure when booted from FW slot B.
The firmware updater will fail if we are booted into FW slot B and we try to update firmware. We shouldn't treat this like a usual update failure because trying again won't help until we reboot. Thus, with this CL, we detect this case and request a reboot from the user. Technically this request is a lie, b/c we are reusing the reboot request mechanism which tells the user an update has been applied and thus must be rebooted. We accept this fib since this situation is very rare: use would have to have 2 FW update updates in a row w/o any extra boots between. Also, fix error code in subprocess. Also, remove execute permissions on a bunch of source files. BUG=chromium-os:14343 TEST=unittests, tested updates on machine that success, fail, have FW B failure Review URL: http://codereview.chromium.org/6880077 Change-Id: I2509c6e1c9c9da3ff1ea27da4861c4850bd4d000
Diffstat (limited to 'action_processor.h')
-rw-r--r--action_processor.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/action_processor.h b/action_processor.h
index 7f7862ab..2ed5f78e 100644
--- a/action_processor.h
+++ b/action_processor.h
@@ -42,6 +42,7 @@ enum ActionExitCode {
kActionCodeNewKernelVerificationError = 16,
kActionCodeSignedDeltaPayloadExpectedError = 17,
kActionCodeDownloadPayloadPubKeyVerificationError = 18,
+ kActionCodePostinstallBootedFromFirmwareB = 19,
kActionCodeOmahaRequestEmptyResponseError = 200,
kActionCodeOmahaRequestXMLParseError = 201,
kActionCodeOmahaRequestNoUpdateCheckNode = 202,