On Fri, 2003-02-14 at 12:41, David Brownell wrote: > Getting low latencies on those OUT transfers will be an issue. > Two transfers in the queue should normally handle it, unless > something delays reporting the first completion long enough to > prevent it from re-issuing in time ... as you have noticed. >
Sorry I didn't give more info.... I was talking about the OUT transfers. We are currently transferring 64 bytes every millisecond, which is the fastest speed that USB 1.0 supports in isochronous mode. We have found the source of this delay though, the computer has an 82801DB motherboard, for which the 2.4.19 kernel has a bug and doesn't allow DMA to be turned on for the hard drive. When we patched that bug, and turned DMA on, we stopped seeing these "gap in isochronous scheduling" errors. Thank you for all of your help, Dan ------------------------------------------------------- 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
