> > - For a successful synchronous unlink, the completion handler did fire
> > before the unlink call returned. Easily proven for HCDs that go
> > through the "hcd.c" logic (*), otherwise you have to take it on faith.
> > (And some older HCD code might bugs here, like not reporting
> > completions.)
>
> Excellent! So why not add some code at the end of usb_unlink_urb that
> polls the urb state (i.e. yield()s) until it is clear that the completion
> handler has finished? Is the problem that the urb could be resubmited in
> the completion handler?
No, that would be an advantage, as we could unlink that urb.
Currently there's no way to tell an urb executing its completion handler
from a finished urb. So we wouldn't have to poll, but could wake the task
doing the unlink from usb_hcd_giveback_urb(). In fact we'd have to.
Regards
Oliver
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
