Drivers without code like that can be easily patched, even before usb_interface.driver is removed.
I should mention that indeed there is no big problem fixing the drivers. But is it the way we want to go?
I think so, yes. Do you have an alternative approach to suggest?
Regardless of the driver model question, the issue is how the usbcore code is inconsistent about when it'll disconnect(). The inconsistency is a problem in its own right, and specifically for usbfs (as you noted) although the cdc and audio drivers are currently fine with it.
- Dave
------------------------------------------------------- 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
