> If you need to have disconnect() called in all cases, feel free > to get rid of usb_interface.driver ... it needs to go someday, > and I'd guess that's making trouble for you. > > I can't see the CDC (ACM, Ethernet) or audio (ALSA, OSS) drivers > getting into trouble with that any time soon, but those are the > only other users of the claim/release calls righ now.
Hi Dave, the obvious thing to do (once intf->driver is thrown away) is to call device_release_driver in usb_driver_release_interface. However this means that disconnect will be called. That is fine for usbfs, but it seems to me that it is no good for usbnet... Comments? Ciao, Duncan. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
