Home
last modified time | relevance | path

Searched refs:probed (Results 1 – 25 of 35) sorted by relevance

12

/f-stack/dpdk/drivers/bus/vmbus/
H A Dvmbus_common.c172 size_t probed = 0, failed = 0; in rte_vmbus_probe() local
176 probed++; in rte_vmbus_probe()
190 return (probed && probed == failed) ? -1 : 0; in rte_vmbus_probe()
/f-stack/dpdk/doc/guides/regexdevs/
H A Dmlx5.rst32 Mellanox mlx5 pci device can be probed by number of different pci devices,
34 be specified as device parameter. The RegEx device can be probed and used with
/f-stack/dpdk/doc/guides/mempool/
H A Docteontx2.rst53 provide ``max_pools`` parameter to the first PCIe device probed by the given
85 configures an NPA LF and attach to the first probed ethdev or eventdev device.
/f-stack/dpdk/drivers/bus/pci/
H A Dpci_common.c339 size_t probed = 0, failed = 0; in pci_probe() local
343 probed++; in pci_probe()
359 return (probed && probed == failed) ? -1 : 0; in pci_probe()
/f-stack/dpdk/doc/guides/nics/
H A Dfail_safe.rst63 When trying to use a PCI device automatically probed by the command line,
95 address of the first of its sub-device to be successfully probed and use it as
97 If no sub-device was successfully probed at initialization, then a random MAC
99 they are probed.
123 If the sub-device ``84:00.0`` is not blocked, it will be probed by the
H A Docteontx.rst113 PKI/PKO PCIe VF devices will be probed and then the vdev device can be created
115 the number of probed/bound PKI/PKO PCIe VF device to DPDK by
/f-stack/dpdk/doc/guides/eventdevs/
H A Docteontx.rst50 SSO PCIe VF devices will be probed and then the vdev device can be created
52 the number of probed/bound SSO PCIe VF device to DPDK by
H A Ddpaa.rst49 probed and then vdev device can be created from the application code by
H A Ddpaa2.rst58 probed and then vdev device can be created from the application code by
/f-stack/freebsd/contrib/device-tree/Bindings/mips/img/
H A Dpistachio.txt14 be probed via CPS, it is not necessary to specify secondary CPUs. Required
/f-stack/freebsd/contrib/device-tree/Bindings/openrisc/opencores/
H A Dor1ksim.txt19 be probed via CPS, it is not necessary to specify secondary CPUs. Required
/f-stack/freebsd/contrib/device-tree/Bindings/reserved-memory/
H A Dqcom,cmd-db.txt10 resource properties may change. These properties are dynamically probed by the
/f-stack/freebsd/contrib/device-tree/Bindings/net/
H A Dbrcm,mdio-mux-iproc.txt13 Every non-ethernet PHY requires a compatible so that it could be probed based
/f-stack/freebsd/contrib/device-tree/Bindings/gpio/
H A Dsodaville.txt10 There is no compatible property for now because the driver is probed via
/f-stack/freebsd/contrib/device-tree/src/mips/mti/
H A Dmalta.dts34 * controller & should be probed first.
/f-stack/dpdk/doc/guides/vdpadevs/
H A Dmlx5.rst43 A Mellanox mlx5 PCI device can be probed by either net/mlx5 driver or vdpa/mlx5
46 By default, the mlx5 device will be probed by the net/mlx5 driver.
/f-stack/dpdk/doc/guides/rawdevs/
H A Ddpaa2_cmdif.rst65 On EAL initialization, dpci devices will be probed and then vdev device
H A Ddpaa2_qdma.rst69 On EAL initialization, dpdmai devices will be probed and populated into the
H A Difpga.rst27 Each instance of IFPGA Rawdev Driver is probed by Intel FpgaDev. In coordination
H A Docteontx2_ep.rst73 On EAL initialization, SDP VF devices will be probed and populated into the
H A Docteontx2_dma.rst94 On EAL initialization, dma devices will be probed and populated into the
/f-stack/dpdk/doc/guides/compressdevs/
H A Docteontx.rst64 probed. To use the PMD in an application, user must:
/f-stack/freebsd/contrib/device-tree/Bindings/i2c/
H A Di2c-pxa-pci-ce4100.txt8 The driver is probed via the PCI-ID and is gathering the information of
/f-stack/freebsd/contrib/device-tree/Bindings/remoteproc/
H A Dst,stm32-rproc.yaml102 If defined, when remoteproc is probed, it loads the default firmware and
/f-stack/freebsd/contrib/device-tree/Bindings/sound/
H A Dst,sta32x.txt23 If specified, the clock will be enabled when the codec is probed,

12