| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/gdb/ |
| H A D | Working-Directory.html | 17 <title>Debugging with GDB: Working Directory</title>
19 <meta name="description" content="Debugging with GDB: Working Directory">
20 <meta name="keywords" content="Debugging with GDB: Working Directory">
64 <a name="Working-Directory"></a>
70 <a name="Your-Program_0027s-Working-Directory"></a>
71 <h3 class="section">4.5 Your Program’s Working Directory</h3>
73 <a name="index-working-directory-_0028of-your-program_0029"></a>
75 initialized with the current working directory specified by the
77 command, then the inferior will inherit <small>GDB</small>’s current working
78 directory as its working directory if native debugging, or it will
[all …]
|
| H A D | Input_002fOutput.html | 30 <link href="Working-Directory.html#Working-Directory" rel="previous" title="Working Directory">
67 …next">Attach</a>, Previous: <a href="Working-Directory.html#Working-Directory" accesskey="p" rel="…
148 …next">Attach</a>, Previous: <a href="Working-Directory.html#Working-Directory" accesskey="p" rel="…
|
| H A D | Environment.html | 29 <link href="Working-Directory.html#Working-Directory" rel="next" title="Working Directory">
67 Next: <a href="Working-Directory.html#Working-Directory" accesskey="n" rel="next">Working Directory…
95 working directory at the time <small>GDB</small> searches the path. If you
173 Next: <a href="Working-Directory.html#Working-Directory" accesskey="n" rel="next">Working Directory…
|
| H A D | Automatically.html | 73 <p>To have <small>GDB</small> set the working language automatically, use
75 then infers the working language. That is, when your program stops in a
77 working language to the language recorded for the function in that
80 does not have a recognized extension), the current working language is
87 case frees you from having to set the working language manually.
|
| H A D | Setting.html | 73 <p>There are two ways to control the working language—either have <small>GDB</small>
76 defaults to setting the language automatically. The working language is
80 <p>In addition to the working language, every source file that
81 <small>GDB</small> knows about has its own working language. For some object
100 …y</a>:</td><td> </td><td align="left" valign="top">Setting the working language manually
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/gdb/ |
| H A D | Working-Directory.html | 17 <title>Debugging with GDB: Working Directory</title>
19 <meta name="description" content="Debugging with GDB: Working Directory">
20 <meta name="keywords" content="Debugging with GDB: Working Directory">
64 <a name="Working-Directory"></a>
70 <a name="Your-Program_0027s-Working-Directory"></a>
71 <h3 class="section">4.5 Your Program’s Working Directory</h3>
73 <a name="index-working-directory-_0028of-your-program_0029"></a>
75 initialized with the current working directory specified by the
77 command, then the inferior will inherit <small>GDB</small>’s current working
78 directory as its working directory if native debugging, or it will
[all …]
|
| H A D | Input_002fOutput.html | 30 <link href="Working-Directory.html#Working-Directory" rel="previous" title="Working Directory">
67 …next">Attach</a>, Previous: <a href="Working-Directory.html#Working-Directory" accesskey="p" rel="…
148 …next">Attach</a>, Previous: <a href="Working-Directory.html#Working-Directory" accesskey="p" rel="…
|
| H A D | Environment.html | 29 <link href="Working-Directory.html#Working-Directory" rel="next" title="Working Directory">
67 Next: <a href="Working-Directory.html#Working-Directory" accesskey="n" rel="next">Working Directory…
95 working directory at the time <small>GDB</small> searches the path. If you
173 Next: <a href="Working-Directory.html#Working-Directory" accesskey="n" rel="next">Working Directory…
|
| H A D | Automatically.html | 73 <p>To have <small>GDB</small> set the working language automatically, use
75 then infers the working language. That is, when your program stops in a
77 working language to the language recorded for the function in that
80 does not have a recognized extension), the current working language is
87 case frees you from having to set the working language manually.
|
| H A D | Setting.html | 73 <p>There are two ways to control the working language—either have <small>GDB</small>
76 defaults to setting the language automatically. The working language is
80 <p>In addition to the working language, every source file that
81 <small>GDB</small> knows about has its own working language. For some object
100 …y</a>:</td><td> </td><td align="left" valign="top">Setting the working language manually
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/pm/ |
| H A D | strategies.rst | 20 designated devices, triggering a transition to the ``working state`` in which
25 The other strategy, referred to as the :doc:`working-state power management
26 <working-state>`, is based on adjusting the power states of individual hardware
27 components of the system, as needed, in the working state. In consequence, if
28 this strategy is in use, the working state of the system usually does not
44 back to the working state can only be started by a limited set of devices, so
53 away from the laptop keyboard, it probably should stay in the working state and
54 use the working-state power management in case it becomes idle, because the user
|
| H A D | suspend-flows.rst | 13 system to get from the working state into one of the supported
19 For those sleep states, the transition from the working state of the system into
23 working state is referred to as *system resume*.
45 The following steps are taken in order to transition the system from the working
54 up after getting back to the working state.
92 would be triggered in the working state of the system (those actions are
124 :ref:`suspend-to-idle <s2idle>` sleep state into the working state:
137 2. Resuming devices and restoring the working-state configuration of IRQs.
146 The working-state configuration of IRQs is restored after the *noirq* resume
167 The following steps are taken in order to transition the system from the working
[all …]
|
| /OK3568_Linux_fs/u-boot/board/keymile/scripts/ |
| H A D | README | 14 This file defines variables for working with rootfs via nfs for powerpc and
19 This file defines architecture specific variables for working with rootfs via
25 This file defines variables for working with rootfs inside the ram for powerpc
30 This file defines architecture specific variables for working with rootfs inside
|
| /OK3568_Linux_fs/kernel/drivers/scsi/ufs/ |
| H A D | ufshcd-pltfrm.h | 20 u32 rx_pwr_pwm; /* rx pwm working pwr */
21 u32 tx_pwr_pwm; /* tx pwm working pwr */
22 u32 rx_pwr_hs; /* rx hs working pwr */
23 u32 tx_pwr_hs; /* tx hs working pwr */
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-bsp/flashrom/flashrom/ |
| H A D | 0001-typecast-enum-conversions-explicitly.patch | 28 - supported_boards[i].working = binfo[i].working;
29 + supported_boards[i].working =
30 + (enum flashrom_test_state) binfo[i].working;
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-kernel/oprofile/oprofile/ |
| H A D | 0010-oprofile-Determine-the-root-home-directory-dynamical.patch | 27 - with this option, your current working directory should be <filename>/root</filename> or a subdi…
29 + with this option, your current working directory should be <filename>~root</filename> or a subdi…
40 - with this option, your current working directory should be <code class="filename">/root</code> o…
42 + with this option, your current working directory should be <code class="filename">~root</code> o…
|
| /OK3568_Linux_fs/yocto/poky/documentation/overview-manual/ |
| H A D | development-environment.rst | 84 are several ways of working in the Yocto Project environment:
268 with whatever upstream branch they are working against. They are also
310 local branches in your working Git repository on the development
313 which you are working. Once you are done with a feature or change and
320 be working on different parts of the same feature. Merging changes
429 local working area (also called a branch) that tracks a specific
447 working branch based on a branch name, your local environment matches
469 create and checkout a local working Git branch based on a tag name. When
472 The most common use is to checkout a working branch that matches a
491 checkout a local working branch based on a tag, your environment matches
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/power/ |
| H A D | tricks.rst | 7 If you want to trick swsusp/S3 into working, you might want to try:
14 * use ext2. At least it has working fsck. [If something seems to go
25 * due to video issues, swsusp should be easier to get working than
|
| H A D | video.rst | 26 whitelist of systems, and automatically selects working method for a
29 whitelist, please try to find a working solution, and submit whitelist
62 to life. It needs text console to be working. Do vbetool vbestate
75 the display working in graphical mode again.
87 chance of working.
89 Table of known working notebooks:
198 Known working desktop systems
|
| /OK3568_Linux_fs/buildroot/package/nginx/ |
| H A D | 0002-auto-feature-add-mechanism-allowing-to-force-feature.patch | 52 + echo " found but is not working"
56 - echo " found but is not working"
90 - echo " found but is not working"
92 + echo " found but is not working"
|
| /OK3568_Linux_fs/kernel/arch/m68k/fpsp040/ |
| H A D | decbin.S | 124 | 1. Copy bcd value in memory for use as a working copy.
138 | ( ) a0: pointer to working bcd value
140 | (*) FP_SCR1: working copy of original bcd value
166 orl #0x40000000,(%a0) |and in working bcd
184 | ( ) a0: pointer to working bcd value
187 | ( ) FP_SCR1: working copy of original bcd value
275 | ( ) a0: pointer to working bcd value
276 | ( ) FP_SCR1: working copy of original bcd value
403 | ( ) a0: pointer to working copy of bcd
477 | ( ) a0: pointer to working bcd value
|
| /OK3568_Linux_fs/u-boot/drivers/ddr/altera/ |
| H A D | sequencer.c | 1548 * @working: If 1, look for working phase/delay, if 0, look for non-working
1551 * @work: Working window position
1552 * @work_inc: Working window increment
1555 * Find working or non-working DQS enable phase setting.
1557 static int sdr_find_phase_delay(int working, int delay, const u32 grp, in sdr_find_phase_delay() argument
1572 if (!working) in sdr_find_phase_delay()
1586 * @working: If 1, look for working phase, if 0, look for non-working phase
1588 * @work: Working window position
1592 * Find working or non-working DQS enable phase setting.
1594 static int sdr_find_phase(int working, const u32 grp, u32 *work, in sdr_find_phase() argument
[all …]
|
| /OK3568_Linux_fs/kernel/arch/riscv/include/asm/ |
| H A D | ptrace.h | 64 /* Helpers for working with the instruction pointer */
77 /* Helpers for working with the user stack pointer */
88 /* Helpers for working with the frame pointer */
|
| /OK3568_Linux_fs/kernel/lib/ |
| H A D | test_linear_ranges.c | 27 * Problem is that testing working code is pointless. And if it is not
28 * working, your test must not assume it is working. You won't catch any bugs
47 * working.
51 * working. And I definitely don't want to add 500+ test cases that break when
|
| /OK3568_Linux_fs/kernel/Documentation/process/ |
| H A D | 6.Followthrough.rst | 22 Working with reviewers
26 developers as they review the code. Working with reviewers can be, for
49 be working on the kernel years from now, but they understand that their
51 working toward the creation of the best kernel they can; they are not
121 patch. Now other developers working with that tree will get the patch by
131 Other times, conflict resolution will involve working with the other
|