Searched refs:located (Results 201 – 225 of 486) sorted by relevance
12345678910>>...20
/openbmc/u-boot/doc/ |
H A D | README.ramboot-ppc85xx | 76 In the 2nd case bootloader has already re-located CCSRBAR to 0xffe00000
|
H A D | README.xtensa | 33 a variant-specific directory located in the arch/xtensa/include/asm
|
H A D | README.memory-test | 51 the ranges is too small and/or badly located) or in critical
|
/openbmc/qemu/docs/devel/ |
H A D | ci-runners.rst.inc | 16 The GitLab CI jobs definition for the custom runners are located under::
|
H A D | reset.rst | 251 located inside the object instance structure. 258 In ``DeviceClass`` and ``BusClass`` the ``ResettableState`` is located
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Certs/CSR/ |
H A D | Create.interface.yaml | 145 The state or province where the organization is located. This
|
/openbmc/linux/Documentation/arch/x86/ |
H A D | boot.rst | 247 Real-mode kernel must be located at 0x90000. 624 The kernel command line can be located anywhere between the end of 625 the setup heap and 0xA0000; it does not have to be located in the 1100 located in the same 64K segment as the real-mode setup code; it is 1104 The kernel command line should not be located below the real-mode 1105 code, nor should it be located in high memory. 1253 recommended that they are located *first*, before the user-specified 1262 located at *segment* offset 0x20 from the start of the real mode
|
/openbmc/linux/Documentation/input/devices/ |
H A D | yealink.rst | 215 :A: The sysfs files are located on the particular usb endpoint. On most
|
/openbmc/linux/tools/perf/pmu-events/ |
H A D | README | 22 Architecture standard JSONs must be located in the architecture root
|
/openbmc/linux/Documentation/networking/dsa/ |
H A D | bcm_sf2.rst | 41 The driver is located in ``drivers/net/dsa/bcm_sf2.c`` and is implemented as a DSA
|
H A D | b53.rst | 16 The driver is located in ``drivers/net/dsa/b53/`` and is implemented as a
|
/openbmc/linux/Documentation/PCI/endpoint/ |
H A D | pci-test-howto.rst | 137 The tool and script will be located in <rootfs>/usr/bin/
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
H A D | Dimm.interface.yaml | 15 Socket on base board where Memory located, for example CPU1_DIMM_B1.
|
/openbmc/linux/Documentation/i2c/busses/ |
H A D | i2c-piix4.rst | 93 device is located at 00:0f.0.
|
/openbmc/linux/Documentation/translations/zh_CN/dev-tools/ |
H A D | kasan.rst | 192 The buggy address is located 123 bytes inside of
|
/openbmc/linux/Documentation/devicetree/bindings/remoteproc/ |
H A D | ti,k3-dsp-rproc.yaml | 53 file located on the firmware search path
|
H A D | ti,pru-rproc.yaml | 67 file located on the firmware search path.
|
/openbmc/linux/Documentation/userspace-api/netlink/ |
H A D | intro-specs.rst | 18 The tool is located at ``tools/net/ynl/cli.py``. It accepts
|
/openbmc/linux/Documentation/accel/ |
H A D | introduction.rst | 64 Furthermore, the drivers will be located in a separate place in the kernel
|
/openbmc/openbmc/poky/meta/recipes-devtools/python/python3/ |
H A D | python3-manifest.json | 49 # This will automatically replace your manifest file located under the Python directory
|
/openbmc/linux/Documentation/fb/ |
H A D | api.rst | 73 Planes are located contiguously in memory. 290 FOURCC definitions are located in the linux/videodev2.h header. However, and
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/toshiba/ |
H A D | spider_net.rst | 86 net eth1: Chain tail located at descr=20 146 net eth1: Chain tail located at descr=255
|
/openbmc/linux/fs/jffs2/ |
H A D | Kconfig | 27 located and fixed, the detailed messages were relegated to level 2.
|
/openbmc/qemu/docs/interop/ |
H A D | vhost-user-gpu.rst | 68 :scanout-id: ``u32``, the scanout where the cursor is located
|
/openbmc/linux/Documentation/PCI/ |
H A D | sysfs-pci.rst | 102 underlying platform supports them. They're located in the PCI class hierarchy,
|
12345678910>>...20