Re: [dpdk-dev] [PATCH v3 1/3] drivers/bus: move driver assignment to end of probing

11/10/2018 17:41, Andrew Rybchenko: > On 10/11/18 6:29 PM, Thomas Monjalon wrote: > > 11/10/2018 15:15, Andrew Rybchenko: > >> On 10/11/18 3:59 PM, Thomas Monjalon wrote: > >>> 11/10/2018 13:54, Andrew Rybchenko: > On 10/11/18 2:45 PM, Thomas Monjalon wrote: > > 11/10/2018 12:53, Andrew Ry

Re: [dpdk-dev] [PATCH v3 1/3] drivers/bus: move driver assignment to end of probing

On 10/11/18 6:29 PM, Thomas Monjalon wrote: 11/10/2018 15:15, Andrew Rybchenko: On 10/11/18 3:59 PM, Thomas Monjalon wrote: 11/10/2018 13:54, Andrew Rybchenko: On 10/11/18 2:45 PM, Thomas Monjalon wrote: 11/10/2018 12:53, Andrew Rybchenko: On 10/8/18 1:09 AM, Thomas Monjalon wrote: The PCI

Re: [dpdk-dev] [PATCH v3 1/3] drivers/bus: move driver assignment to end of probing

11/10/2018 15:15, Andrew Rybchenko: > On 10/11/18 3:59 PM, Thomas Monjalon wrote: > > 11/10/2018 13:54, Andrew Rybchenko: > >> On 10/11/18 2:45 PM, Thomas Monjalon wrote: > >>> 11/10/2018 12:53, Andrew Rybchenko: > On 10/8/18 1:09 AM, Thomas Monjalon wrote: > > The PCI mapping requires to

Re: [dpdk-dev] [PATCH v3 1/3] drivers/bus: move driver assignment to end of probing

On 10/11/18 3:59 PM, Thomas Monjalon wrote: 11/10/2018 13:54, Andrew Rybchenko: On 10/11/18 2:45 PM, Thomas Monjalon wrote: 11/10/2018 12:53, Andrew Rybchenko: On 10/8/18 1:09 AM, Thomas Monjalon wrote: The PCI mapping requires to know the PCI driver to use, even before the probing is done. T

Re: [dpdk-dev] [PATCH v3 1/3] drivers/bus: move driver assignment to end of probing

11/10/2018 13:54, Andrew Rybchenko: > On 10/11/18 2:45 PM, Thomas Monjalon wrote: > > 11/10/2018 12:53, Andrew Rybchenko: > >> On 10/8/18 1:09 AM, Thomas Monjalon wrote: > >>> The PCI mapping requires to know the PCI driver to use, > >>> even before the probing is done. That's why the PCI driver is

Re: [dpdk-dev] [PATCH v3 1/3] drivers/bus: move driver assignment to end of probing

On 10/11/18 2:45 PM, Thomas Monjalon wrote: 11/10/2018 12:53, Andrew Rybchenko: On 10/8/18 1:09 AM, Thomas Monjalon wrote: The PCI mapping requires to know the PCI driver to use, even before the probing is done. That's why the PCI driver is referenced early inside the PCI device structure. See

Re: [dpdk-dev] [PATCH v3 1/3] drivers/bus: move driver assignment to end of probing

11/10/2018 12:53, Andrew Rybchenko: > On 10/8/18 1:09 AM, Thomas Monjalon wrote: > > The PCI mapping requires to know the PCI driver to use, > > even before the probing is done. That's why the PCI driver is > > referenced early inside the PCI device structure. See > > 1d20a073fa5e ("bus/pci: refere

Re: [dpdk-dev] [PATCH v3 1/3] drivers/bus: move driver assignment to end of probing

On 10/8/18 1:09 AM, Thomas Monjalon wrote: The PCI mapping requires to know the PCI driver to use, even before the probing is done. That's why the PCI driver is referenced early inside the PCI device structure. See 1d20a073fa5e ("bus/pci: reference driver structure before mapping") However the r

Re: [dpdk-dev] [PATCH v3 1/3] drivers/bus: move driver assignment to end of probing

On 10/8/18 1:09 AM, Thomas Monjalon wrote: The PCI mapping requires to know the PCI driver to use, even before the probing is done. That's why the PCI driver is referenced early inside the PCI device structure. See 1d20a073fa5e ("bus/pci: reference driver structure before mapping") However the r

[dpdk-dev] [PATCH v3 1/3] drivers/bus: move driver assignment to end of probing

The PCI mapping requires to know the PCI driver to use, even before the probing is done. That's why the PCI driver is referenced early inside the PCI device structure. See 1d20a073fa5e ("bus/pci: reference driver structure before mapping") However the rte_driver does not need to be referenced in r