[CC: list pruned] On Wed, 28 Apr 2004, Oliver Neukum wrote:
> > But the first case still applies. (As does the case of maverick drivers > > like Bluetooth that don't use usb_free_urb().) So there has to be a way > > for a driver to wait until an URB's completion handler has finished. > > That's the need addressed by usb_wait_for_urb(). > > Is there anybody using a synchronous unlink who doesn't want that? Not as far as I know. Of course, I'm not familiar with every single USB driver. :-) Does usblp ever do a synchronous unlink and then reuse the URB immediately afterward? > > finished. That's why usb_wait_for_urb() is needed. > > But is very poorly implemented. Can you come up with something better in terms of both space and time? Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
