On Thu, 9 Sep 2004, Toralf Lund wrote: > Something I forgot to mention earlier: I often see evidence of reset > signalling at the point where the problems occurs. Could that be > something initiated by the host/driver? If it is, how am I supposed to > respond?
The USB core will initiate reset signalling when the port-enabled feature turns off. The most likely causes for that are electromagnetic interference (EMI) or a bad cable connection. Another possible cause is a defective device that transmits when it shouldn't. A message should show up in the system log whenever this happens. Also, some drivers may initiate a port reset. But since this is your driver, presumably you would know if it called usb_reset_device(). Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
