> > I've put in a printk to check the error code, it's -110, and that is > > supposed to be ETIMEDOUT. According to ohci.h, this code is returned > > on TD_DEVNOTRESP.. but now, I'm out of clues. > There are two main reasons for a device not to respond to a packet: (1) > the device's firmware has crashed; (2) noise in the USB data lines > prevents the computer from recognizing the response or prevents the device > from recognizing the original packet. Hm, as every now and then, the transmit actually succeeds, I would suppose that 2 is the problem. The cable isn't shielded, so that may in fact be quite propable.
Yours, Florian ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
