| /external/vboot_reference/firmware/lib/ |
| D | vboot_api_init.c | 27 uint32_t recovery = VBNV_RECOVERY_NOT_REQUESTED; in VbInit() local
114 VbNvGet(&vnc, VBNV_RECOVERY_REQUEST, &recovery); in VbInit()
115 VBDEBUG(("VbInit sees recovery request = %d\n", recovery)); in VbInit()
116 if (VBNV_RECOVERY_NOT_REQUESTED != recovery) in VbInit()
127 if (VBNV_RECOVERY_NOT_REQUESTED == recovery && in VbInit()
129 recovery = VBNV_RECOVERY_RO_FIRMWARE; in VbInit()
137 recovery = VBNV_RECOVERY_RO_MANUAL; in VbInit()
143 shared->recovery_reason = (uint8_t)recovery; in VbInit()
144 VBDEBUG(("VbInit now sets shared->recovery_reason = %d\n", recovery)); in VbInit()
195 recovery, is_hw_dev)); in VbInit()
[all …]
|
| D | vboot_firmware.c | 58 int recovery = VBNV_RECOVERY_RO_UNSPECIFIED; in LoadFirmware() local
333 recovery = VBNV_RECOVERY_RO_INVALID_RW; in LoadFirmware()
345 recovery = best_check; in LoadFirmware()
353 recovery : VBNV_RECOVERY_NOT_REQUESTED); in LoadFirmware()
361 shared->recovery_reason = recovery; in LoadFirmware()
|
| /external/vboot_reference/scripts/keygeneration/ |
| D | create_new_keys.sh | 20 --4k-recovery Use 4k key size for the recovery key
21 --4k-recovery-kernel Use 4k key size for the recovery kernel data
59 --4k-recovery)
62 --4k-recovery-kernel)
|
| /external/vboot_reference/utility/ |
| D | chromeos-tpm-recovery-test | 9 rm -rf tpm-recovery-test-workdir
10 mkdir tpm-recovery-test-workdir
11 cd tpm-recovery-test-workdir
28 export DOT_RECOVERY=.recovery
30 ctr=../chromeos-tpm-recovery
33 ctr=chromeos-tpm-recovery
40 echo > .recovery
|
| /external/autotest/server/site_tests/firmware_RecoveryButton/ |
| D | control.ec_wp | 9 PURPOSE = "Press recovery button and check for recovery boot"
10 CRITERIA = "This test will fail if firmware does not enter recovery mode"
22 recovery button pressed and reboots. It then triggers recovery mode by
|
| D | control.dev | 9 PURPOSE = "Press recovery button and check for recovery boot"
10 CRITERIA = "This test will fail if firmware does not enter recovery mode"
22 recovery button pressed and reboots. It then triggers recovery mode by
|
| D | control | 9 PURPOSE = "Press recovery button and check for recovery boot"
10 CRITERIA = "This test will fail if firmware does not enter recovery mode"
22 recovery button pressed and reboots. It then triggers recovery mode by
|
| /external/autotest/server/site_tests/firmware_UserRequestRecovery/ |
| D | control.ec_wp | 9 PURPOSE = "Request recovery mode and check it next reboot."
10 CRITERIA = "This test will fail if firmware does not enter recovery mode"
22 a recovery mode on next boot by setting the crossystem recovery_request
23 flag. It then triggers recovery mode by unplugging and plugging in the USB
|
| D | control | 9 PURPOSE = "Request recovery mode and check it next reboot."
10 CRITERIA = "This test will fail if firmware does not enter recovery mode"
22 a recovery mode on next boot by setting the crossystem recovery_request
23 flag. It then triggers recovery mode by unplugging and plugging in the USB
|
| D | control.dev | 9 PURPOSE = "Request recovery mode and check it next reboot."
10 CRITERIA = "This test will fail if firmware does not enter recovery mode"
22 a recovery mode on next boot by setting the crossystem recovery_request
23 flag. It then triggers recovery mode by unplugging and plugging in the USB
|
| /external/autotest/server/site_tests/firmware_CorruptBothKernelAB/ |
| D | control.dev | 10 CRITERIA = "This test will fail if firmware does not enter recovery mode"
20 This test corrupts both kernel A and B and and checks for recovery boot.
25 and enters recovery mode. This test then checks the success of the
26 recovery boot.
|
| D | control | 10 CRITERIA = "This test will fail if firmware does not enter recovery mode"
20 This test corrupts both kernel A and B and and checks for recovery boot.
25 and enters recovery mode. This test then checks the success of the
26 recovery boot.
|
| /external/autotest/server/site_tests/platform_InstallRecoveryImage/ |
| D | control | 15 This test installs a specified recovery image onto a servo-connected DUT.
16 This is useful for testing the recovery process and imaging servo-connected
18 Here is the command to install a recovery image;
|
| /external/autotest/server/site_tests/firmware_LegacyRecovery/ |
| D | control | 9 PURPOSE = "Servo based test to Verify recovery request at Remove Screen."
10 CRITERIA = "This test will fail if the recovery at Remove screen is success."
21 (built by "build_image --test"). It recovery boots to the USB image and sets
|
| /external/autotest/server/site_tests/firmware_DevTriggerRecovery/ |
| D | control | 9 PURPOSE = "Servo based recovery boot triggered by pressing a key at dev screen"
10 CRITERIA = "This test will fail if firmware does not enter recovery mode"
22 trigger recovery boot and checks the success of it.
|
| /external/autotest/server/site_tests/firmware_CorruptBothFwSigAB/ |
| D | control.dev | 10 CRITERIA = "This test will fail if firmware does not enter recovery mode"
23 fails and enters recovery mode. This test then checks the success of the
24 recovery boot.
|
| D | control | 10 CRITERIA = "This test will fail if firmware does not enter recovery mode"
23 fails and enters recovery mode. This test then checks the success of the
24 recovery boot.
|
| /external/autotest/server/site_tests/firmware_UpdateKernelVersion/ |
| D | control | 15 4. After recovery, device can't successfully restart.
16 5. Kernel version does not recover to original version after recovery.
30 version. Here also tries to reboot with kernel b after recovery. If sccuess,
|
| /external/autotest/server/site_tests/firmware_UpdateKernelDataKeyVersion/ |
| D | control | 17 4. After recovery, device can't successfully restart.
18 5. Kernel datakey version does not recover to original version after recovery.
33 recovery. If sccuess, reboot with kernel a.
|
| /external/clang/test/Index/ |
| D | crash-recovery-modules.m | 7 // CHECK-CRASH: crash-recovery-modules.m:16:9:{16:2-16:14}: fatal error: could not build module 'Cr…
13 // REQUIRES: crash-recovery
28 // Check that libclang crash-recovery works; both with a module building crash...
|
| /external/clang/test/FixIt/ |
| D | fixit-static-object-decl.m | 1 // Objective-C recovery
6 // Objective-C++ recovery
|
| D | fixit-missing-method-return-type.m | 1 // Objective-C recovery
6 // Objective-C++ recovery
|
| D | fixit-objc-message.m | 1 // Objective-C recovery
6 // Objective-C++ recovery
|
| /external/autotest/server/site_tests/firmware_FWupdate/ |
| D | control | 13 RO+RW firmware update using chromeos-firmwareupdate --mode=recovery
20 Default mode is recovery, add mode=factory to use factory mode.
|
| /external/autotest/server/site_tests/firmware_ECLidShutdown/ |
| D | control | 21 - Verifies that closing lid in recovery will shutdown DUT
23 - Verifies that closing lid in recovery will not shutdown DUT
|