Greg KH wrote:
On Thu, Jun 09, 2011 at 05:25:10PM +0300, Felipe Balbi wrote:
Hi,
Alan Stern wrote:
How do you deal with the fact that after this change,
modprobe gadget_driver
will fail if the UDC driver isn't already loaded? This could break
some userspace scripts.
The driver should be loaded by udev. There could be some breakage if
I like the idea of depending on udev. I remember I had a discussion with
Greg before and he told me we should rely on udev for these things.
Yes, we should rely on udev for automatically loading the correct
drivers when the hardware is found.
But, how are we telling userspace that this driver is needed? That
needs to be in place for modprobe (which is what udev calls) to be able
to know which module to load. I don't see that change here, but I might
be missing it.
The net2280 which Alan was referring to is a PCI device which is probed
the usual way. The majority are platform_driver which add a
platform_device in their board code. A few driver miss a
MODULE_ALIAS("platform:...") but that should be it. I have a patch for
that which needs some testing.
So that should work IMHO. What we miss is the information which function
driver to load but we are talking about UDC (device) driver atm.
thanks,
greg k-h
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
