Re: [dpdk-dev] [PATCH] rte, eal: Rename pci_update_device and make it public

Hi Thomas, That's OK. Hope that the need of usage can be considered in the new framework. -Original Message- From: Thomas Monjalon [mailto:thomas.monja...@6wind.com] Sent: Friday, March 10, 2017 1:58 AM To: Yang, Ziye Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH] rte, eal: R

Re: [dpdk-dev] [PATCH] rte, eal: Rename pci_update_device and make it public

2017-02-13 10:53, Ziye Yang: > The reaon is that sometimes we only like to rebound the > kernel driver or VFIO or UIO or other drivers for > this device after rte_eal_detach function. Function > rte_eal_pci_probe_one not only updates the device but > also probes the rte_eal_driver for this device,

[dpdk-dev] [PATCH] rte, eal: Rename pci_update_device and make it public

The reaon is that sometimes we only like to rebound the kernel driver or VFIO or UIO or other drivers for this device after rte_eal_detach function. Function rte_eal_pci_probe_one not only updates the device but also probes the rte_eal_driver for this device, it is not flexible. Signed-off-by: Ziy