On Wed, Feb 19, 2003, Greg KH <[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) > > Yes, some drivers do this, (the keyspan driver is one, and I think the > visor driver also wants to.)
Ok, I have a keyspan to test with. > > > > As long as the rules about who owns the URB when and where are clearly > > > > defined (and implemented), then reference counting may not be necessary. > > > > > > Sure, but even when the HCD "owns" the urb, it can callback into the > > > driver, and the driver better still be in memory while the urb is alive. > > > > Yes, that is a concern, but it's a driver issue. The driver needs to > > make sure this doesn't happen. > > But what about drivers that fire off urbs and don't keep a pointer to > them around? They don't know if all of their urbs are completed or not, > nor should they really care. The visor driver is one good example of > this. Sounds broken to me. Someone needs to keep track of it, and it's not the core right now. I think they should care simply because they allocated the memory and submitted the URB. It's very irresponsible to expect someone else to deal with your mess :) 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
