HomeSort by relevance Sort by last modified time
    Searched full:recovery (Results 101 - 125 of 1562) sorted by null

1 2 3 45 6 7 8 91011>>

  /external/llvm/lib/Support/
CrashRecoveryContext.cpp 1 //===--- CrashRecoveryContext.cpp - Crash Recovery ------------------------===//
51 /// \brief Called when the separate crash-recovery thread was finished, to
64 assert(!Failed && "Crash recovery context already failed!");
168 // Lookup the current thread local recovery object.
236 // crash recovery context, and install signal handlers to invoke HandleCrash on
240 // reliable fashion -- if we get a signal outside of a crash recovery context we
241 // simply disable crash recovery and raise the signal again.
251 // Lookup the current thread local recovery object.
255 // We didn't find a crash recovery context -- this means either we got a
257 // outside of a crash recovery context, or something else went horribl
    [all...]
  /external/vboot_reference/firmware/2lib/
2api.c 63 * Check for recovery. Note that this function returns void, since
64 * any errors result in requesting recovery.
68 /* Return error if recovery is needed */
70 /* Always clear RAM when entering recovery mode */
2misc.c 102 * need to go to recovery.
104 * Set a recovery reason and subcode only if they're not already set.
105 * If recovery is already requested, it's a more specific error code
108 VB2_DEBUG("Need recovery, reason: %#x / %#x\n", reason, subcode);
126 * store a recovery reason.
144 * Read the current recovery request, unless there's already been a
150 /* Clear the recovery request so we don't get stuck in recovery mode */
156 * hit this code path if recovery mode has already been
158 * the original reason for going into recovery mode
    [all...]
  /system/sepolicy/
recovery_refresh.te 1 # android recovery refresh log manager
postinstall.te 35 # No domain other than update_engine and recovery (via update_engine_sideload)
38 neverallow { domain -update_engine -recovery } postinstall:process { transition dyntransition };
update_engine_common.te 2 # background daemon and the recovery tool to sideload an update.
11 # Allow to set recovery options in the BCB. Used to trigger factory reset when
  /external/vboot_reference/firmware/include/
vboot_nvstorage.h 57 * Request recovery mode on next boot; see VBNB_RECOVERY_* below for
90 /* More details on recovery reason */
124 /* Recovery reason codes for VBNV_RECOVERY_REQUEST */
125 /* Recovery not requested. */
128 * Recovery requested from legacy utility. (Prior to the NV storage spec,
129 * recovery mode was a single bitfield; this value is reserved so that scripts
130 * which wrote 1 to the recovery field are distinguishable from scripts whch
131 * use the recovery reasons listed here.
134 /* User manually requested recovery via recovery button *
    [all...]
  /docs/source.android.com/src/devices/tech/ota/
device_code.jd 28 <p>The recovery system includes several hooks for inserting device-specific
39 used by both the recovery binary and the package-building tools. You can
43 <p><code>device/yoyodyne/tardis/recovery.fstab</code></p>
52 /recovery emmc /dev/block/platform/s3c-sdhci.0/by-name/recovery
66 recovery. MTD is not actually mounted, but the mount point is used as a key to
74 recovery. Similar to the mtd type, eMMc is never actually mounted, but the
84 applies only to mounting filesystems in recovery; the main system is free to
85 mount them anywhere. The directories <code>/boot</code>, <code>/recovery</code>,
91 <p>Starting in Android 3.0, the recovery.fstab file gains an additiona
    [all...]
  /bootable/recovery/
device.h 28 // the recovery user interface for this device. You should not
33 // Called when recovery starts up (after the UI has been obtained
38 // Called from the main thread when recovery is at the main menu
41 // recovery will be at the main menu with it invisible after an
42 // unsuccessful operation [ie OTA package failure], or if recovery
79 // Perform a recovery action selected from the menu.
97 // or when the user boots into recovery image manually and selects the
112 // It returns the Device object that recovery should use.
  /bootable/recovery/otafault/
Android.mk 29 LOCAL_C_INCLUDES := bootable/recovery
41 LOCAL_C_INCLUDES := bootable/recovery
  /bootable/recovery/tools/recovery_l10n/res/values/
strings.xml 23 <!-- Displayed on the screen when the user has gotten into recovery
25 users (especially developers) may boot into recovery mode
  /device/google/dragon/
fstab.dragon 11 /dev/block/platform/700b0600.sdhci/by-name/recovery /recovery emmc defaults defaults
  /external/antlr/antlr-3.4/runtime/Python/tests/
t035ruleLabelPropertyRef.py 14 # no error recovery yet, just crash!
23 # no error recovery yet, just crash!
t037rulePropertyRef.py 14 # no error recovery yet, just crash!
23 # no error recovery yet, just crash!
t039labels.py 14 # no error recovery yet, just crash!
23 # no error recovery yet, just crash!
  /external/autotest/server/site_tests/firmware_ECLidShutdown/
control 21 - Verifies that closing lid in recovery will shutdown DUT
23 - Verifies that closing lid in recovery will not shutdown DUT
  /external/autotest/server/site_tests/firmware_EventLog/
firmware_EventLog.py 66 if self._has_event(r'Developer Mode|Recovery Mode|Sleep| Wake'):
83 if self._has_event(r'Recovery Mode|Sleep| Wake'):
89 logging.info('Verifying eventlog behavior in recovery mode')
101 not self._has_event(r'Chrome OS Recovery Mode \| Recovery Button')):
102 raise error.TestError('Missing required event in recovery mode.')
104 raise error.TestError('Incorrect event logged in recovery mode.')
116 if self._has_event(r'System |Developer Mode|Recovery Mode'):
  /external/autotest/server/site_tests/firmware_FWupdate/
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_FwScreenCloseLid/
firmware_FwScreenCloseLid.py 36 """Wait and trigger TO_NORM or RECOVERY INSERT screen and close lid."""
95 "RECOVERY INSERT screen (old). Then close lid to "
108 logging.info("Request recovery boot. When the RECOVERY INSERT "
122 logging.info("Request recovery boot again. When the recovery "
144 logging.info("Expected normal mode and request recovery boot. "
145 "Because an USB stick is inserted, a RECOVERY REMOVE "
  /external/autotest/server/site_tests/platform_ServoPowerStateController/
control.usb 23 off -> recovery mode boot from USB
24 recovery mode -> off
  /external/clang/test/FixIt/
fixit-missing-method-return-type.m 1 // Objective-C recovery
6 // Objective-C++ recovery
fixit-objc-message.m 1 // Objective-C recovery
6 // Objective-C++ recovery
  /build/tools/releasetools/
img_from_target_files 24 Include only the bootable images (eg 'boot' and 'recovery') in
85 if bootable_only and image not in ("boot.img", "recovery.img"):
107 "recovery.img", "recovery.img", OPTIONS.input_tmp, "RECOVERY")
img_from_target_files.py 24 Include only the bootable images (eg 'boot' and 'recovery') in
85 if bootable_only and image not in ("boot.img", "recovery.img"):
107 "recovery.img", "recovery.img", OPTIONS.input_tmp, "RECOVERY")
  /external/autotest/server/site_tests/firmware_DevTriggerRecovery/
firmware_DevTriggerRecovery.py 14 Servo based recovery boot test triggered by pressing enter at dev screen.
19 trigger recovery boot and checks the success of it.
80 "and trigger recovery boot at dev screen. ")
89 logging.info("Expected recovery boot and disable dev switch.")
92 'mainfw_type': 'recovery',

Completed in 121 milliseconds

1 2 3 45 6 7 8 91011>>