> It's often good to compare _both_ UHCI drivers when you run > into HCD dependent behaviors. We're trying to get away from > having two, and that's one of the goals of the 2.5 conversion to use > a new "hcd" framework and share code between all the HCDs.
I'll try a new kernel ASAP to see if that fixes any of the problems. I didn't realize there were two UHCI drivers .... how do I switch between them? > > I can accept the fact that for case #5 - we're simply running out of > > time to receive all of the data. By the time we've queued up the URB > > to get the last chunk of data, we've lost some data? Or, more likely, > > we've lost some data somewhere from the first to the last chunk, but > > since there is lots of data, the buffers are all full the urb until > > the last one. > > I'm not clear what the failure mode is for #5. Those test parameters > shouldn't matter, unless your device is (inappropriately) expecting > bulk transfers to succeed with some particular timing. I just checked with the folks who are building this hardware and there definitely are some timing expectations as the modem does very little internal buffering. So, it appears that if you don't grab data fast enough, it might just disappear. Thanks, -Chris _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
