> > > > 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. > > The number of device drivers would need to increase dramatically. > > > > But of course there may be vendor specific devices whose drivers should set > > > configuration. We need to accomodate both. The question is, how exactly? > > > > Certainly there are two categories of drivers: generic and vendor. While my > > proposal is primarily oriented toward vendor drivers, the architecture is > > equally applicable to both. > > We'd better call them whole device and interface drivers. > > > My goal is to simplify the vendor development environment as much as > > possible, since these are the people who must be convinced to "get with the > > program" ;-) > > How serious is the problem? > > Regards > Oliver >
I don't know how serious the problem is, but I believe it does exist. May I suggest the more appropriate question would be: How easy can we make the driver development process for the vendors? Linux driver development represents an expense incurred by the vendor to support a niche market. It is incumbent upon us to facilitate the process to the greatesst extent possible if we expect Linux to be successful in the marketplace. We should not be asking "Is it too horribly difficult?" Rather we should ask "Can we make it any easier?" FWIW 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
