On Thursday 21 October 2004 01:38, Guennadi Liakhovetski wrote: > Hi, thanks for the answers. > > Hm, what, if someone needs both (no, I don't atm:-))? I see the choice is > made in usbcore at compile time with #ifdef CONFIG_..._UB... If I > understand it correct, that's because usbcore builds a table of > > USB class <-> driver
See how the MODULE_DEVICE_TABLE stuff works with the driver model core. It's not just classes that are associated with drivers, and the association isn't bidirectional. And even if there's a device table entry, the driver probe routine can still refuse to look at a device -- maybe based on information it can see, but which isn't listed in the device table. If two drivers both have device table entries compatible with a given device, one will be probed first. If it grabs the device, the other won't be probed. > pairs. Wouldn't it be better to leave this decision to the hotplug system > altogether? The Linux driver model doesn't much like the notion that a given logical device have a choice of drivers. Also, there's no way to change the binding of device and driver using sysfs; you can "rmmod" one and "modprobe" the other, but that may not work well and it'd affect all devices using that driver, not just the one you were looking at. - Dave ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
