I use the IRQ transfer in high speed. qh->period=1 (frame).
As long as the qh can be reused everything is fine...
If not then we end up here: This loop loops virtually forever with period=1:
frame = qh->period - 1;
do {
for (uframe = 0; uframe < 8; uframe++) {
status = check_intr_schedule (ehci,
frame, uframe, qh,
&c_mask);
if (status == 0)
break;
}
} while (status && --frame);... as the decrement happens too early. Seems to me so. What about:
(status && frame--)
/Bernd
P.S.: However, this does not solve my problem that just now only one INT transfer per frame is allowed. Is this right, Dave?
--
http://www.cn.stir.ac.uk/~bp1
mailto:[EMAIL PROTECTED]
------------------------------------------------------- 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
