On Thu, Feb 20, 2003, Oliver Neukum <[EMAIL PROTECTED]> wrote: > > > Does the existing serial driver submit URBs after the device is > > physically removed? (Like if an application still has an fd open when > > the device was removed) > > Of course it does. _Any_ driver will do so. The window between > physical and logical disconnection is unavoidable, if only because > of the polling interval of the hub driver.
You are correct, but I meant something else, sorry. How about this: Does the existing serial driver submit URBs after the disconnect() callback has finished for the device? > > Although, that may piss of the sysadmin. If the device is gone and no > > applications are using it, the driver should be able to be removed. But > > this is just a sysadmin user interface thing. > > In a major way. We need stated rules on when drivers can be unloaded. > Besides, what are you to do if incrementing a usage count in > usb_submit_urb() fails ? By definition you cannot return to the driver. Heh, good point. It's probably dangerous to do that. JE ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
