Home
last modified time | relevance | path

Searched refs:shown (Results 1 – 25 of 449) sorted by relevance

12345678910>>...18

/openbmc/u-boot/doc/device-tree-bindings/misc/
H A Dfs_loader.txt17 ubi in device tree source as shown in below:
20 sata and ubi as shown in below:
/openbmc/linux/tools/perf/Documentation/
H A Dcallchain-overhead-calculation.txt3 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 DREADME.bootmenu31 <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
H A DREADME.commands.spl31 nand write <adress shown by spl export> 0x680000 0x20000
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-security/keyutils/files/
H A D0002-tests-Use-head-n1-for-busybox-compatibility.patch21 # check the session keyring ID is shown
30 # check the session keyring ID is shown
/openbmc/linux/Documentation/trace/
H A Dhisi-ptt.rst171 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/linux/Documentation/RCU/Design/Memory-Ordering/
H A DTree-RCU-Memory-Ordering.rst197 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
288 One set of code paths shown on the left invokes ``rcu_accelerate_cbs()``
342 counter, as shown below:
370 to the newly advanced value from the ``rcu_state`` structure, as shown
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:
[all …]
/openbmc/linux/Documentation/devicetree/bindings/bus/
H A Dti,da850-mstpri.txt15 Example for da850-lcdk is shown below.
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DGlulxe3 …ou retain a notice in your program or documentation which mentions my name and the URL shown above.
H A DBitstream-Charter8 as shown below on all unmodified copies of the 4 Charter Type 1 fonts.
/openbmc/qemu/docs/system/
H A Dimages.rst63 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 Dtarget-rx.rst19 Example of ``qemu-system-rx`` usage for RX is shown below:
/openbmc/pldm/pldmtool/
H A DREADME.md49 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/u-boot/board/freescale/ls2080a/
H A DREADME21 not support 48-bit VA (for e.g. < Linux 3.18) by appending mem=2048M, as shown
/openbmc/linux/Documentation/admin-guide/media/
H A Dpci-cardlist.rst53 .. [#] 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/u-boot/doc/driver-model/
H A Dfs_firmware_loader.txt27 defined in fs-loader node as shown in below:
39 device, it can be described in FDT as shown in below:
/openbmc/linux/arch/arm/boot/dts/sigmastar/
H A Dmstar-infinity3.dtsi16 // overclock frequencies below, shown to work fine up to 1.3 GHz
/openbmc/openbmc/poky/meta/classes-recipe/
H A Dimage-container.bbclass23 # only be shown for the recipes actually requested to build, rather
/openbmc/docs/architecture/
H A Dinterface-overview.md22 and service shown.
28 details from the unit file may be shown, such as the program which implements a
247 | | -+- many more (not shown here) |
263 This section lists each interface and service shown in this document. The intent
286 maintains a logically separate network from the host, as shown in this diagram:
306 direct connection external to the host, as shown in this diagram:
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/lxdm/lxdm/
H A D0001-greeter-set-visible-when-switch-to-input-user.patch7 password. At this time, the user name input is shown as '*' rather than
/openbmc/linux/Documentation/pcmcia/
H A Ddriver.rst9 runtime as shown below::
/openbmc/openbmc-test-automation/tools/
H A Dmyffdc.robot6 ... Logs will be generated as shown below
/openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libdata/
H A Dlibdata-hexdump-perl_0.02.bb7 (all others are shown as single dots).\
/openbmc/openbmc-test-automation/
H A DCONTRIBUTING.md190 - As shown in the following example, if your keyword has any arguments,
195 description text as shown in the example below.
409 are a relative or absolute path (as shown in the examples above). A file
445 are a relative or absolute path (as shown in the examples above). A dir
491 coded in the order shown.
564 - As shown in the prior example, if your function has any arguments, include a
766 a relative or absolute path (as shown in the examples above). A file path
801 a relative or absolute path (as shown in the examples above). A dir path
/openbmc/linux/drivers/greybus/
H A DKconfig9 ARA project, a module phone system, but has shown up in other

12345678910>>...18