> On Mer, 2003-06-04 at 23:19, [EMAIL PROTECTED] wrote: > > > A device may have several interfaces in its configurations. Which driver > > > shall decide? And who shall decide which driver is to decide? > > > > A good example of a manufactured problem. In my proposal, there is only one > > driver for a given device, so your questions disappear. > > This works fine for some devices - and horribly badly when the device is > a mix of generic and custom interfaces. A single driver doesn;t have to > mean a single kernel interface - you can be both sound card and > video for example >
Hi Alan, This conversation is becoming very complex, with multiple threads addressing different aspects of the question. I did mention in one of the other postings that multiple drivers were not precluded. It would be perfectly valid to register multiple drivers for the same VID/PID combination. This would be the exception, but it would certainly support the situations which you suggested. Thanks for your response. Best regards. Leigh Bassett ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
