On Sun, 10 Aug 2003, David Brownell wrote:
That is, given that this logic works correctly (it did when I tested it), this logic can also be the core of a synchronous usbcore call that provides driver developers a flexibility they should have had all along: users can ^C out of driver waits, processes can be kicked out of 'D' wait.
Would it be worthwhile adding a capability like this into the hcd glue layer, so that an URB could be submitted with a nonzero value in its "timeout" field and it would work regardless of the HCD? That would simplify several things.
We don't need HCD glue support for _synchronous_ requests, which are what this patch affects. All the necessary support exists already.
For async URB submissions, I don't recall any drivers needing timeouts. If there were many that needed it, usbcore would be a reasonable place for it to live ... but I'd just as soon see the urb->timeout field vanish, since it's clearly something that can be layered on top.
- Dave
Alan Stern
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
