On Wed, 2004-07-07 at 01:50, Pete Zaitcev wrote: > On Tue, 06 Jul 2004 23:36:26 +0200 > Axel Waggershauser <[EMAIL PROTECTED]> wrote: > > > following problem: After several hours (>10) of continuous bulk > > transfers from the device to the host, I get a completion call with an > > URB status == -84. The controller is a VIA UHCI running 2.6.7 with one > > patch: I changed the FSBR_DELAY from HZ/20 to HZ/2 to "support" large > > transfer buffers. > > [EMAIL PROTECTED] linux-2.6.7-usb]$ find drivers/usb -name '*.[hc]' | LANG=C xargs > grep EILSEQ | more
Thanks (could have done that myself :-)). The uhci11d.pdf says that the TD_CTRL_CRCTIMEO bit gets set on a CRC error detected on the host side or on a timeout generated from the device side but this should merely cause the host controller to perform a retry as long as the error counter in the TD is > 0. (Thats how I understand it.) How can I find out if the UHCI controller was set to perform a retry or to immediately bail out. Is there a default policy that may be changed or is it fixed? Thanks, Axel. ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
