Searched full:follow (Results 1 – 25 of 2131) sorted by relevance
12345678910>>...86
53 /* ports 1-3 follow after this */56 /* ports 5-7 follow after this */60 /* ports 1-3 follow after this */62 /* ports 5-7 follow after this */68 /* ports 1-3 follow after this */71 /* ports 5-7 follow after this */75 /* ports 1-3 follow after this */78 /* ports 5-7 follow after this */
72 /* ports 1-3 follow after this */75 /* ports 5-7 follow after this */79 /* ports 1-3 follow after this */81 /* ports 5-7 follow after this */84 /* ports 1-3 follow after this */87 /* ports 5-7 follow after this */91 /* phys 1-3 follow after this */94 /* phys 1-3 follow after this */
13 …"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this …35 …"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this …57 …"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this …79 …"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this …101 …"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this …123 …"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this …145 …"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this …167 …"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this …189 …"action": "Follow the Set Up procedure to complete the common and specific prerequisites for this …
259 BIT(0) = follow HW0_EN signal260 BIT(1) = follow HW1_EN signal261 BIT(2) = follow HW2_EN signal262 BIT(3) = follow HW3_EN signal271 BIT(0) = follow HW0_EN signal272 BIT(1) = follow HW1_EN signal273 BIT(2) = follow HW2_EN signal274 BIT(3) = follow HW3_EN signal275 BIT(4) = follow PMIC awake state
261 /* res_source_index, res_source optional fields follow */288 * Optional fields follow immediately:330 * Optional fields follow immediately:348 * Optional fields follow immediately:366 * Optional fields follow immediately:387 * Optional fields follow immediately:407 * Optional fields follow immediately:424 * Optional fields follow immediately:443 * Optional fields follow immediately:463 * Optional fields follow immediately:
21 - rockchip,hdmi_audio_source: hdmi audio source that is described as follow24 - rockchip,hdmi_video_source: hdmi video source that is described as follow27 - rockchip,hdcp_enable: hdmi hdcp function is described as follow30 - rockchip,cec_enable: hdmi cec function is described as follow
19 #define MS_NOSYMFOLLOW 256 /* Do not follow symlinks */68 #define MOVE_MOUNT_F_SYMLINKS 0x00000001 /* Follow symlinks on from path */69 #define MOVE_MOUNT_F_AUTOMOUNTS 0x00000002 /* Follow automounts on from path */71 #define MOVE_MOUNT_T_SYMLINKS 0x00000010 /* Follow symlinks on to path */72 #define MOVE_MOUNT_T_AUTOMOUNTS 0x00000020 /* Follow automounts on to path */
107 <p>If you want to follow the child process instead of the parent process,108 use the command <code>set <span class="nolinebreak">follow-fork-mode</span></code><!-- /@w -->.113 <dt><code>set follow-fork-mode <var>mode</var></code></dt>133 <dt><code>show follow-fork-mode</code></dt>152 <code>follow-fork-mode</code>) will be detached and allowed to run 159 <code>follow-fork-mode</code>) is debugged as usual, while the other198 You can change this behaviour with the <code>set <span class="nolinebreak">follow-exec-mode</s…204 <dt><code>set follow-exec-mode <var>mode</var></code></dt>209 <p><code>follow-exec-mode</code> can be:261 <p><code>follow-exec-mode</code> is supported in native mode and
134 "The Option keyword requires 1 or 2 quoted strings to follow it."142 "The %s keyword requires a quoted string to follow it."144 "The %s keyword requires a number to follow it."146 "The %s keyword requires a positive integer to follow it."148 "The %s keyword requires a boolean to follow it."150 "The ZAxisMapping keyword requires 2 positive numbers or X or Y to follow it."
178 -x exclude filenames that follow from listing\n";184 + -x exclude filenames that follow from listing\n\247 + "error: a valid character encoding should follow the -I argument"));255 + "error: a valid character encoding should follow the -I argument"));283 + "error: a valid character encoding should follow the -I argument"));291 + "error: a valid character encoding should follow the -O argument"));347 + "error: a valid character encoding should follow the -I argument"));355 + "error: a valid character encoding should follow the -I argument"));383 + "error: a valid character encoding should follow the -I argument"));391 + "error: a valid character encoding should follow the -O argument"));
17 -pwrkey: Specifies the subnode pwrkey and should follow the19 -resin: Specifies the subnode resin and should follow the22 The rest of the properties should follow the generic reboot-mode description
37 -f, --follow Trace child processes87 [--follow] [--from FROMLIST] [--output FILENAME] [--to TOLIST]113 -f | --fo | --fol | --foll | --follo | --follow)127 do_ambiguous '--from' '--follow'
269 …1109 | 41,38,35,32,30,28,| 44,40,37,34,32,30,| follow DDR4 | 50,46,42,38,36, | follow LP4 | …275 | RK3566/RK3568 | 50,45,41,38,36,33,| 55,50,46,42,39,37,| follow DDR4 | 57,52,48,44,41, | 81,72,65…280 …| X | X | 240,120,80,60, | follow LP4 | follow LP4 | follow LP…285 | RK3528 | 60,55,50,47,44,41,| 62,57,52,49,45,43,| follow DDR4 | 67,62,57,53,49, | 77,69,63…295 … | 34,48 | 34,40,48,60,80 | 40,48,60,80,120,240 | follow LP4 | follow LP4 |313 …09 | 58,52,48,44,41, | 55,50,46,43,40,38, | follow DDR4 | 62,56,52,48,44,41,| follow LP4 | …319 | RK3566/RK3568 | 50,45,41,38,36,33,| 55,50,46,42,39,37, | follow DDR4 | 57,52,48,44,41, | 81,72…324 … X | X | 0,240,120,80, | follow LP4 | follow LP4 | follow LP…329 | RK3528 | 60,55,50,47,44,41,| 62,57,52,49,45,43, | follow DDR4 | 67,62,57,53,49, | 77,69…338 …20 | 0,34,40,48,60,120 | 0,60,120,240 | 0,40,48,60,80,120,240 | follow LP4 | follow LP4 |
139 Follow up145 Linux kernel maintainers expect bug reporters to be able to follow up on149 never follow up on a request to try out a fix.152 on a supported kernel, even if you can't follow up with retests. Follow
; > > > % > 3 > > > > > > $ > > ' > > > ...
57 /* parse response: context command do not follow the common response */ in as10x_cmd_get_context()115 /* parse response: context command do not follow the common response */ in as10x_cmd_set_context()129 * - AUTO : 0x2 => eLNA follow hysteresis parameters177 * Since the contex command response does not follow the common
3 SUMMARY = "X11 eyes that follow the mouse cursor demo"5 follow the location of the mouse cursor around the screen."
227 - The timings follow the CEA-861 Digital TV Profile standard229 - The timings follow the VESA Discrete Monitor Timings standard231 - The timings follow the VESA Coordinated Video Timings standard233 - The timings follow the VESA Generalized Timings Formula standard235 - The timings follow the SDI Timings standard.
164 follow standard semantics.190 follow standard semantics.199 follow standard semantics.216 follow standard semantics.226 follow standard semantics.388 follow standard semantics.421 follow standard semantics.548 configuration change to be allowed. To do this, it may follow the `Drain`560 related ``CAPTURE`` buffers are given to the client, the client must follow the
21 #define LOOKUP_FOLLOW 0x0001 /* follow links at the end */25 #define LOOKUP_DOWN 0x8000 /* follow mounts in the starting point */26 #define LOOKUP_MOUNTPOINT 0x0080 /* follow mounts in the end */
37 dependency). If you want to follow these links40 --exclude-devlinks Don't follow device links when tracking probe43 --exclude-parents Don't follow parent devices when tracking probe125 # They can also have cycles. So, don't follow them.
13 Initial packets follow the classic forwarding path, once the flow enters the31 follow the classic forwarding path unless the user explicitly instruct packets72 neigh_xmit(). Fragmented traffic is passed up to follow the classic forwarding