21/09/2018 13:53, Gaëtan Rivet: > On Thu, Sep 20, 2018 at 06:11:44PM +0200, Thomas Monjalon wrote: > > 19/09/2018 18:03, Gaetan Rivet: > > > The vdev bus parses a field "driver", matching > > > a vdev driver name with one passed as follows: > > > > > > "bus=vdev,driver=xxxx" > > > > I think the property should be "name". > > We already have a "driver" category. > > So it may be "bus=vdev,name=mytap/driver=tap" > > > > Until now we were using the name of the driver as a prefix for > > the device name because it was the only way of knowing the driver to use. > > With a richer syntax like above, this restriction can be removed. > > Do you want all buses to read the driver= key and use it to know which > driver to probe, or is it an exception of the vdev bus?
Good point. Yes, if the driver= key is provided, the bus should respect it. It may allow to have 2 different drivers supporting the same PCI ids, and let the user override the default driver to use.
