Dan Parks wrote:
On Thu, 2003-02-13 at 14:43, Georg Acher wrote:
"iso_find_start: gap in seamless isochronous scheduling"
The causes for this message can be:
- Too much scheduled URBs (i.e. with the new URB, there would be more than
1024 frames "running")
- Not enough URBs running (eg. only 2). At the completion of the first URB,
it's absolutely too late to submit the second one...
We only had 2 URB's, and that was the problem. The reason why we only
had 2, was because the less URB's you have, the lower delay you have. I
guess we're going to go to 3 URBs. Thanks a lot for your help.
What delay that would increase with the number of urbs queued? I'd
think tolerance for irq delays would increase ... you always need to
keep enough queued to handle your maximum IRQ latency.
- Dave
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
