On Wed, 5 Jul 2006, Christopher Montgomery wrote: > The resubmission is in ehci-q.c:qh_completions(); it is not checking > to see if the device is disconnected (is this possible?
No. > ) before > deciding the endpoint EPROTO fault calls for tearing it down and > setting it back up. Active/submitted URBs potentially have nothing to > do with it; it is happening even when my devices are idle. I'm not terribly familiar with ehci-hcd. Where in qh_completions() does the code tear something down and then set it back up again? What does it tear down? In fact, where in qh_completions() does the code even check for -EPROTO? When the devices are idle, how can qh_completions() possibly have any work to do at all? > Is this part of what you're referring to as a high level driver? No. The higher-level driver is the one that submits URBs. Examples are usb-storage and usb-hid. Alan Stern Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
