| /openbmc/linux/Documentation/devicetree/bindings/ata/ |
| H A D | ceva,ahci-1v84.yaml | 44 The fields for the above parameter must be as shown below:-
56 The fields for the above parameter must be as shown below:-
68 The fields for the above parameter must be as shown below:-
80 The fields for the above parameter must be as shown below:-
90 The fields for the above parameter must be as shown below:-
102 The fields for the above parameter must be as shown below:-
114 The fields for the above parameter must be as shown below:-
126 The fields for the above parameter must be as shown below:-
|
| /openbmc/u-boot/doc/device-tree-bindings/misc/ |
| H A D | fs_loader.txt | 17 ubi in device tree source as shown in below:
20 sata and ubi as shown in below:
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | callchain-overhead-calculation.txt | 3 The overhead can be shown in two columns as 'Children' and 'Self' when
100 So '\_\_libc_start_main' and 'main' are shown first since they have
104 Since v3.16 the 'children' overhead is shown by default and the output
|
| /openbmc/u-boot/doc/ |
| H A D | README.bootmenu | 31 <title> is the text of the menu entry shown on the console
44 will be CONFIG_BOOTDELAY. If delay is 0, no menu entries will be shown on
46 be called immediately. If delay is less then 0, bootmenu will be shown and
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-security/keyutils/files/ |
| H A D | 0002-tests-Use-head-n1-for-busybox-compatibility.patch | 21 # check the session keyring ID is shown
30 # check the session keyring ID is shown
|
| /openbmc/linux/Documentation/devicetree/bindings/bus/ |
| H A D | ti,da850-mstpri.txt | 15 Example for da850-lcdk is shown below.
|
| /openbmc/linux/Documentation/trace/ |
| H A D | hisi-ptt.rst | 171 8 bit. Current supported types and related values are shown below:
187 supported are shown below:
195 shown below:
212 Current supported formats and related values are shown below:
220 (Header DW0-3 shown below). For example, the TLP header for Memory
221 Reads with 64-bit addresses is shown in PCIe r5.0, Figure 2-17;
222 the header for Configuration Requests is shown in Figure 2.20, etc.
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Glulxe | 3 …ou retain a notice in your program or documentation which mentions my name and the URL shown above.
|
| /openbmc/linux/Documentation/RCU/Design/Memory-Ordering/ |
| H A D | Tree-RCU-Memory-Ordering.rst | 197 shown below, which is one of several functions that enforce ordering of
275 portion of RCU's grace period guarantee is shown in the following
285 period until a later call to ``rcu_accelerate_cbs()``, as shown in the
342 counter, as shown below:
410 non-idle CPUs report their own quiescent states, as shown in the
425 its leaf ``rcu_node`` lock. Therefore, all execution shown in this
462 traverses up the ``rcu_node`` tree as shown at the bottom of the
486 effects are as shown below:
508 corresponding CPU hotplug operations. The ordering effects are shown
530 shown below:
[all …]
|
| /openbmc/u-boot/board/freescale/ls2080a/ |
| H A D | README | 21 not support 48-bit VA (for e.g. < Linux 3.18) by appending mem=2048M, as shown
|
| /openbmc/openbmc/poky/meta/classes-recipe/ |
| H A D | image-container.bbclass | 23 # only be shown for the recipes actually requested to build, rather
|
| /openbmc/linux/arch/arm/boot/dts/sigmastar/ |
| H A D | mstar-infinity3.dtsi | 16 // overclock frequencies below, shown to work fine up to 1.3 GHz
|
| /openbmc/qemu/docs/system/ |
| H A D | images.rst | 63 A VM snapshot is made of a VM state info (its size is shown in
68 not shown by ``info snapshots`` because the associated disk sectors are
|
| H A D | target-rx.rst | 19 Example of ``qemu-system-rx`` usage for RX is shown below:
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/lxdm/lxdm/ |
| H A D | 0001-greeter-set-visible-when-switch-to-input-user.patch | 7 password. At this time, the user name input is shown as '*' rather than
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/Decorator/ |
| H A D | PowerSystemInputs.interface.yaml | 4 shown by implementing this interface under a multi-object path, such as
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
| H A D | Cable.interface.yaml | 16 a cable, such as optical or copper. The cable type can be shown in
|
| /openbmc/linux/Documentation/devicetree/bindings/media/ |
| H A D | renesas,drif.yaml | 15 representation of DRIF interfacing with a master device is shown below.
158 # When interfacing with a third party tuner device with two data pins as shown
215 # When interfacing with a third party tuner device with one data pin as shown
|
| /openbmc/pldm/pldmtool/ |
| H A D | README.md | 49 with the **-h** help option as shown below:
97 command name with **-h** argument as shown below.
244 Enable verbosity with **-v** flag as shown below.
|
| /openbmc/linux/Documentation/pcmcia/ |
| H A D | driver.rst | 9 runtime as shown below::
|
| /openbmc/openbmc-test-automation/tools/ |
| H A D | myffdc.robot | 6 ... Logs will be generated as shown below
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/ |
| H A D | OriginatedBy.interface.yaml | 10 OriginatorType. The originator id can be shown in user interfaces but
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | fs_firmware_loader.txt | 27 defined in fs-loader node as shown in below:
39 device, it can be described in FDT as shown in below:
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | pci-cardlist.rst | 53 .. [#] some of the drivers have sub-drivers, not shown at this table
95 Some of those drivers support multiple devices, as shown at the card
|
| /openbmc/linux/drivers/greybus/ |
| H A D | Kconfig | 9 ARA project, a module phone system, but has shown up in other
|