On Mon, 2004-12-20 at 10:28 -0500, Alan Stern wrote: > On Mon, 20 Dec 2004, Ed Tomlinson wrote: > > > Its not that they just enable it. Its that it has side effects. I enable > > it to support > > one device - it then 'devnaps' other devices that usbstorage supports _much_ > > better. Is there some way it could work in reverse. eg. let ub bind only > > if > > usbstorage does not, possibly making usbstorage a _little_ more conservative > > if ub is present? > > Unfortunately there isn't any way to define which driver should bind to a > device, if they are both capable of controlling it. Maybe there should > be. It might not be too hard to add a sysfs interface for that sort of > thing.
This is a neverending battle with ALSA and OSS modules claiming the same device, resulting in bizarre behavior. You could argue that it's user or vendor error but that doesn't change the flood of bug reports on alsa-user. I am sure the ALSA developers would welcome a generic solution for this problem. Lee ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
