Searched full:reliably (Results 1 – 25 of 39) sorted by relevance
12
31 specific applications to reliably identify the driver.
140 means applications cannot *reliably* scan for loaded or installed
109 This will reliably suppress packet loss. The LAPB protocol will123 This will not reliably avoid packet loss, but the probability
93 be reliably detected in ndo_fix_features. In this case, the callback
209 be reliably poll()'d or read() from while in this mode.
55 May be omitted if EDID works reliably.
72 to work reliably.
22 the messages can always be reliably determined.
103 such that the cache can reliably recover from unclean shutdown;
70 Reason for this is that the RTC is the only reliably available piece of
49 but interrupt behaviour is not guaranteed to work reliably. In test mode, the
34 Features cannot be probed reliably through other means. When a feature
108 reliably.
87 this information to detect a stalled bus more reliably, for example.
84 userspace is able to reliably determine which PMC the event is scheduled on.
107 * Provide a detect function if and only if a chip can be detected reliably.
171 reliably if only connected two machines are connected using FireWire.
50 reliably unwind across interrupts and exceptions. Frame pointer based
36 Users that want to reliably query this information more than once have
42 estimate reliably the duration of audio buffers when handling
116 If you can reliably trigger the stall, ftrace can be quite helpful.
222 such as locks that were taken to be reliably released. There is *no*
551 and t2 are known to be fairly close, we can reliably compute the
436 - Livepatch works reliably only when the dynamic ftrace is located at
350 devices that advertise 'discard_zeroes_data' will not reliably return