/openbmc/u-boot/examples/standalone/ |
H A D | README.smc91111_eeprom | 13 4. Other things you can do with this 14 5. Things to be done. 22 each node of a network. When things are not unique - bad things 47 it is not a good idea to start doing things on the network before the 48 MAC address is set, this example will do things over serial. 53 you specify things to load as is not the load address specified 141 should be blank, and allow you to set things one time. 174 4. Other things that you can do
|
/openbmc/linux/Documentation/power/ |
H A D | opp.rst | 117 /* Do things */ 123 /* Do cpufreq things */ 125 /* Do remaining things */ 263 /* do things */ 269 /* do other things */ 280 /* do things.. */ 288 /* do other things */ 296 /* do things.. */ 306 /* Do things */ 319 /* Do other things */
|
/openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libstrictures/ |
H A D | libstrictures-perl_2.000006.bb | 5 Things like the importer in \"use Moose\" don't help me because they turn \ 15 syntax (and not so obvious mistakes that cause things to accidentally compile \ 17 cost of blowing things up on another machine. \
|
/openbmc/qemu/tests/functional/qemu_test/ |
H A D | tuxruntest.py | 2 # that tuxrun (www.tuxrun.org) does. This tool is used by things like 63 # Occasionally we need extra devices to hook things up 124 then do a few things on the console. Trigger a shutdown and 150 special with the command line we can process most things using
|
/openbmc/linux/Documentation/process/ |
H A D | 6.Followthrough.rst | 28 process. Life can be made much easier, though, if you keep a few things in 56 the kernel. One job the maintainers do is to keep things looking 65 understand what the reviewer is trying to say. If possible, fix the things 75 agree with the reviewer, take some time to think things over again. It can 99 What if you've tried to do everything right and things still aren't going 118 things. In particular, there may be more than one tree - one, perhaps, 192 Other things that can happen
|
H A D | howto.rst | 56 of doing things. 130 not have a stable API within the kernel, including things like: 385 you want to bring up, before you post it to the list. A lot of things 448 again, sometimes things get lost in the huge volume. 465 of a dozen things you should correct. This does **not** imply that your 475 development environments. Here are a list of things that you can try to 478 Good things to say regarding your proposed changes: 487 Bad things you should avoid saying: 532 The reasons for breaking things up are the following: 602 All of these things are sometimes very hard to do. It can take years to [all …]
|
H A D | management-style.rst | 57 needs to do is to turn the big and painful ones into small things where 71 things that can't be undone. Don't get ushered into a corner from which 219 Things will go wrong, and people want somebody to blame. Tag, you're it. 242 5) Things to avoid 257 Similarly, don't be too polite or subtle about things. Politeness easily
|
/openbmc/linux/Documentation/driver-api/ |
H A D | frame-buffer.rst | 15 that are user defined. With fb_var_screeninfo, things such as depth 25 importance for fb_monospecs. This allowed for forbidden things such as 27 fb_monospecs prevents such things, and if used correctly, can prevent a
|
/openbmc/linux/arch/x86/include/uapi/asm/ |
H A D | debugreg.h | 14 /* Define a few things for the status register. We can use this to determine 31 /* Now define a bunch of things for manipulating the control register. 65 /* The second byte to the control register has a few special things.
|
/openbmc/linux/Documentation/trace/ |
H A D | ftrace-design.rst | 15 code relies on for proper functioning. Things are broken down into increasing 46 We'll make the assumption below that the symbol is "mcount" just to keep things 74 typically the bare minimum with checking things before returning. That also 130 things. 185 be able to skimp on things saved/restored (usually just registers used to pass 235 You need very few things to get the syscalls tracing in an arch. 345 patching multiple things. First, only functions that we actually want to trace
|
/openbmc/docs/ |
H A D | hw-vendor-repos-policy.md | 61 fixes for things such as new compiler updates 142 hardware, or other things that only exist on that platform). 151 reviewers, and it follows the tip of upstream yocto master. All of these things 155 other things like the latest compiler.
|
/openbmc/linux/Documentation/devicetree/bindings/mfd/ |
H A D | mfd.txt | 10 silicon) that handles analog drivers for things like audio amplifiers, LED 11 drivers, level shifters, PHY (physical interfaces to things like USB or
|
/openbmc/linux/arch/sparc/include/asm/ |
H A D | pbm.h | 12 * To put things into perspective, consider sparc64 with a few PCI controllers. 34 /* Now things for the actual PCI bus probes. */
|
/openbmc/linux/Documentation/gpu/amdgpu/ |
H A D | driver-core.rst | 17 the SoC itself rather than specific IPs. E.g., things like GPU resets 24 their interface to interact with those common components. For things 62 various things including paging and GPU page table updates. It's also 105 SoC and for things like init/fini/suspend/resume, more or less just
|
/openbmc/linux/Documentation/security/ |
H A D | self-protection.rst | 53 temporary exceptions to this rule to support things like instruction 117 things like compat, user namespaces, BPF creation, and perf limited only 159 the function returns. Other defenses include things like shadow stacks. 207 It should be noted that things like the stack canary discussed earlier 212 Blinding literal values for things like JITs, where the executable 270 addresses or other sensitive things like canary values).
|
/openbmc/u-boot/doc/ |
H A D | README.dns | 49 things. 58 For some helpful things that can be related to DNS in U-Boot,
|
/openbmc/linux/drivers/misc/echo/ |
H A D | echo.h | 40 things like modem line equalisers and line echo cancellers. There it works very 42 very poorly for things like speech echo cancellation, where the signal level 88 and the environment is not, things will be OK. Clearly, it is easy to tell when
|
/openbmc/linux/Documentation/dev-tools/kunit/ |
H A D | faq.rst | 70 Unfortunately, there are a number of things which can break, but here are some 71 things to try. 91 enable/disable things with ``make ARCH=um menuconfig`` or similar, and then
|
/openbmc/linux/include/uapi/linux/ |
H A D | rfkill.h | 143 * accessed them, but things should've continued to work. 147 * did all kinds of fun things not in line with this scheme: 155 * things to no longer work correctly on old and new kernels.
|
/openbmc/linux/Documentation/translations/zh_CN/cpu-freq/ |
H A D | core.rst | 97 /* Do things */ 101 /* Do other things */
|
/openbmc/linux/drivers/gpu/drm/msm/disp/mdp5/ |
H A D | mdp5_smp.h | 39 * 1) in _prepare_commit() we configure things (via read-modify-write) 42 * 2) in _complete_commit(), after vblank/etc, we clear things for the
|
/openbmc/linux/arch/x86/platform/efi/ |
H A D | efi_thunk_64.S | 9 * has been called. This simplifies things considerably as compared with 16 * 64-bit virtual address space. Things like the stack and instruction
|
/openbmc/linux/Documentation/translations/zh_TW/cpu-freq/ |
H A D | core.rst | 95 /* Do things */ 99 /* Do other things */
|
/openbmc/linux/arch/arm64/boot/dts/qcom/ |
H A D | sc7280-chrome-common.dtsi | 8 * things that will hold true for any conceivable Chrome design 69 /* The PMIC PON code isn't compatible w/ how Chrome EC/BIOS handle things. */
|
/openbmc/linux/tools/verification/rv/src/ |
H A D | trace.c | 87 * things required for the tracing, such as the local events and 114 * things such as the priority of the tracer's threads. in trace_instance_init()
|