| /f-stack/freebsd/contrib/device-tree/Bindings/usb/ |
| H A D | ulpi.txt | 4 Phys that are behind a ULPI connection can be described with the following
|
| /f-stack/freebsd/vm/ |
| H A D | vm_fault.c | 1161 int ahead, behind, cluster_offset, rv; in vm_fault_getpages() local
1197 behind = 0; in vm_fault_getpages()
1202 behind = 0; in vm_fault_getpages()
1216 behind = ulmin(cluster_offset, in vm_fault_getpages()
1222 *behindp = behind; in vm_fault_getpages()
1281 int ahead, behind, faultcount; in vm_fault() local
1477 rv = vm_fault_getpages(&fs, nera, &behind, &ahead); in vm_fault()
1479 faultcount = behind + 1 + ahead; in vm_fault()
1590 faultcount > 0 ? behind : PFBAK, in vm_fault()
1620 PAGE_SIZE + behind * PAGE_SIZE); in vm_fault()
|
| /f-stack/freebsd/contrib/device-tree/Bindings/i2c/ |
| H A D | i2c-gate.txt | 23 Kasei ak8975 compass behind a gate.
|
| H A D | i2c-mux-ltc4306.txt | 19 multiplexers on the bus and the devices behind them use same I2C addresses.
|
| H A D | i2c-mux-pca954x.txt | 32 multiplexers on the bus and the devices behind them use same I2C addresses.
|
| H A D | i2c-mux-gpmux.txt | 37 However, I2C transactions to devices behind all I2C multiplexers connected
|
| /f-stack/dpdk/doc/guides/tools/ |
| H A D | devbind.rst | 67 …If your device is behind a PCI-to-PCI bridge, the bridge will then be part of the IOMMU group in w…
68 … should also be unbound from the bridge PCI device for VFIO to work with devices behind the bridge.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/crypto/ |
| H A D | hisilicon,hip07-sec.txt | 22 - iommus: The SEC units are behind smmu-v3 iommus.
|
| /f-stack/freebsd/contrib/device-tree/src/arm/ |
| H A D | at91-ariag25.dts | 77 /* TWD2+TCLK2 hidden behind ethernet, so no i2c2 */
|
| H A D | da850-lego-ev3.dts | 75 * The EV3 has two built-in bi-color LEDs behind the buttons.
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | af_packet.rst | 46 For the full details behind PACKET_MMAP's structures and settings, consider
|
| H A D | af_xdp.rst | 11 For the full details behind AF_XDP socket, you can refer to
|
| H A D | virtio.rst | 453 ring, driver event suppression and device event suppression. The idea behind
|
| /f-stack/freebsd/contrib/device-tree/Bindings/memory-controllers/ |
| H A D | exynos-srom.yaml | 14 extra properties, describing the bus behind it, should be specified.
|
| /f-stack/freebsd/x86/conf/ |
| H A D | NOTES | 98 # so it's "hidden" behind a flag:
|
| /f-stack/freebsd/contrib/device-tree/Bindings/pci/ |
| H A D | pci.txt | 19 may be assigned to root buses behind different host bridges. The domain
|
| /f-stack/dpdk/doc/guides/linux_gsg/ |
| H A D | linux_drivers.rst | 243 If your device is behind a PCI-to-PCI bridge,
246 for VFIO to work with devices behind the bridge.
|
| /f-stack/freebsd/contrib/zlib/doc/ |
| H A D | txtvsbin.txt | 57 The idea behind this algorithm relies on two observations.
|
| H A D | algorithm.txt | 106 and there will only be one table look up. (That's whole idea behind data
|
| /f-stack/dpdk/doc/guides/howto/ |
| H A D | debug_troubleshoot.rst | 133 * If the TX rate is falling behind the application fill rate, identify if
185 * If the desired burst dequeue falls behind the actual dequeue, the enqueue
|
| /f-stack/freebsd/contrib/device-tree/Bindings/mtd/ |
| H A D | brcm,brcmnand.txt | 46 interrupts multiplexed behind another custom piece of
|
| /f-stack/freebsd/contrib/device-tree/Bindings/remoteproc/ |
| H A D | ti,omap-remoteproc.yaml | 17 The processor cores in the sub-system are usually behind an IOMMU, and may
|
| /f-stack/freebsd/contrib/device-tree/Bindings/fpga/ |
| H A D | fpga-region.txt | 291 bridges behind the scenes. No FPGA Bridge devices are needed for full
|
| /f-stack/freebsd/contrib/zlib/ |
| H A D | FAQ | 236 As far as we know, no. In fact, that was originally the whole point behind
|
| /f-stack/freebsd/contrib/zstd/ |
| H A D | CONTRIBUTING.md | 90 …re to point out any design and architectural decisions that you made and the rationale behind them.
|