On 7/5/06, Alan Stern <[EMAIL PROTECTED]> wrote: > ehci-hcd doesn't schedule endpoints; it schedules QHs.
Effectively the same thing. An INTR endpoint maps to one and only one QH in the schedule. As for ISO endpoints, it schedules the stream. Each ISO endpoint has one and exactly one stream. So, saying 'it doesn't schedule endpoints' is splitting the finest of semantic hairs. > It won't > reschedule a QH that has no pending URBs (or at least, it won't do this > more than once for any QH). Each -EPROTO error will terminate an URB, so > the activity can't continue indefinitely unless URBs continue to be > submitted. The hub is plugged in doing nothing. It has no connected devices. I unplug it. I log multiple EPROTO errors and see resubmission attemps as well as schedule teardown/setup. Apparently there are always pending URBs, so we're once again splitting hairs. > That's why the URB submitter should throttle its activity. ehci-hcd can't > do much about it. ...except that ehci-hcd is what is resubmitting the URB. Monty 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
