2005/9/7, David Brownell <[EMAIL PROTECTED]>:
> > Just to be sure, you mean if "URB1" is done at frameX then "URB2" must
> > be done at frameX + URB2->intervall ? Can you point out the section of
> > USB spec that explains this, please ?
>
> Forget about URB2->interval; it's an error in the device driver if
> that's not the same as URB1->interval (or URB3->interval etc), and
> the HCDs generally won't bother testing for that error.
>
well, actually my question wasn't on interval value but on the
schedule of periodic transfers: if "URB1" is done at frameX, does
"URB2" have to be send at frameX + endpoint_interval or can it be sent
at frameX as well ? I can't find this point in USB spec...
> > It seems to appear in "finish_request" when no
> > more (periodic and async) transfers are pending.
>
> Again, what possible benefits could come from deferring that?
>
well finish_request is called in interrupt context, but
disable_endpoint is not...
Thanks
--
Franck
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
