Home
last modified time | relevance | path

Searched refs:behind (Results 1 – 25 of 195) sorted by relevance

12345678

/openbmc/qemu/docs/
H A Dpci_expander_bridge.txt32 - a pxb host bridge attached to NUMA 1 with an e1000 behind it
33 - a pxb host bridge attached to NUMA 0 with an e1000 behind it
34 - a pxb host bridge not attached to any NUMA with a hard drive behind it.
49 …However, the bus behind is exposed through ACPI as a primary PCI bus and starts a new PCI hierarch…
50 The interrupts from devices behind the PXB are routed through this device the same as if it were a
56 - All the devices behind the bridge will use bridge's IO/MEM windows compacting
/openbmc/linux/fs/ubifs/
H A Dmaster.c27 int behind; in ubifs_compare_master_node() local
43 behind = hmac_offs + UBIFS_MAX_HMAC_LEN; in ubifs_compare_master_node()
45 if (UBIFS_MST_NODE_SZ > behind) in ubifs_compare_master_node()
46 return memcmp(m1 + behind, m2 + behind, UBIFS_MST_NODE_SZ - behind); in ubifs_compare_master_node()
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-ata21 connected, the number of links behind it.
43 If a link is behind a port, the directory name is linkX, where X is ata_port_id
44 of the port. If a link is behind a PM, its name is linkX.Y where X is
121 "none" if no device was found behind the link.
/openbmc/openbmc/poky/meta/recipes-core/glibc/glibc/
H A D0023-tests-Skip-2-qemu-tests-that-can-hang-in-oe-selftest.patch6 qemumips and qemuppc were leaving stale processes behind after
9 Disable them so that there are no stale processes left behind.
/openbmc/openbmc/meta-quanta/meta-q71l/
H A DREADME.md6 This platform is currently supported, although often behind.
/openbmc/linux/Documentation/devicetree/bindings/usb/
H A Dulpi.txt4 Phys that are behind a ULPI connection can be described with the following
/openbmc/obmc-console/docs/
H A Dmux-support.md3 In some hardware designs, multiple UARTS may be available behind a Mux, which
6 For example, let's say behind `/dev/ttyS0` there are `UART1` and `UART2`, behind
/openbmc/linux/Documentation/driver-api/mei/
H A Dnfc.rst6 Some Intel 8 and 9 Series chipsets support NFC devices connected behind
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/liblogging/
H A Dliblogging_1.0.6.bb7 sophisticated "behind the scenes" with better support for multiple threads \
/openbmc/linux/drivers/clk/versatile/
H A DKconfig29 Express platforms hidden behind its configuration infrastructure,
/openbmc/linux/drivers/fsi/
H A DKconfig60 This option enables a FSI master that is present behind an OPB bridge
70 behind an IBM I2C Responder (I2CR) chip. The I2CR is an I2C device
/openbmc/linux/Documentation/arch/x86/
H A Dbooting-dt.rst21 otherwise like interrupt routing or a list of devices behind an I2C bus.
/openbmc/linux/Documentation/gpu/rfc/
H A Di915_gem_lmem.rst11 * Merge the uAPI bits behind special CONFIG_BROKEN(or so) flag
/openbmc/linux/Documentation/driver-api/pci/
H A Dp2pdma.rst17 only supports doing P2P when the endpoints involved are all behind the
61 memory behind it, its driver could add support as a P2P provider and
123 effects behind it. Thus, the order of loads and stores should not be important
/openbmc/openbmc/poky/meta/recipes-devtools/libtool/
H A Dlibtool-2.5.4.inc4 (such as shared libraries) behind a consistent interface."
/openbmc/linux/Documentation/devicetree/bindings/i2c/
H A Di2c-mux-ltc4306.txt19 multiplexers on the bus and the devices behind them use same I2C addresses.
/openbmc/linux/Documentation/filesystems/
H A Dinotify.rst18 What is the design decision behind not tying the watch to the open fd of
29 What is the design decision behind using an-fd-per-instance as opposed to
/openbmc/openbmc/poky/meta/recipes-devtools/python/python3/
H A Ddeterministic_imports.patch9 Secondly, empty directories left behind by previous modules might be looked at. This
/openbmc/linux/Documentation/devicetree/bindings/crypto/
H A Dhisilicon,hip07-sec.txt22 - iommus: The SEC units are behind smmu-v3 iommus.
/openbmc/linux/drivers/usb/isp1760/
H A DKconfig14 where the chip itself is behind a PLB to simulate such
/openbmc/u-boot/doc/
H A DREADME.cfi40 * is located behind a FPGA (Xilinx DS617) and needs the Intel type
/openbmc/linux/arch/arm64/boot/dts/marvell/
H A Dac5-98dx25xx.dtsi208 * Dedicated section for devices behind 32bit controllers so we
211 behind-32bit-controller@7f000000 {
/openbmc/linux/Documentation/firmware-guide/acpi/
H A Denumeration.rst9 devices behind serial bus controllers.
21 - Devices behind real busses where there is a connector resource
30 The ACPI implementation enumerates devices behind busses (platform, SPI,
186 Slave devices behind SPI bus have SpiSerialBus resource attached to them.
261 The slaves behind I2C bus controller only need to add the ACPI IDs like
263 any slave devices behind the controller device once the adapter is
/openbmc/linux/Documentation/maintainer/
H A Dconfigure-git.rst41 history can find related discussions and rationale behind a certain change.
/openbmc/obmc-console/
H A DREADME.md58 In some hardware designs, multiple UARTS may be available behind a Mux. Please

12345678