On Mon, 22 Sep 2003, David Brownell wrote:
In this case, because it's not "EHCI + USB 2.0 hub", it's still using the OHCI companion controller. So that wasn't a new case.
Ok. Here's the broken case with an added usb-2 hub in between. It is indeed a bit different.
Yes. Instead of getting 64/128 bytes transferred, with -EOVERFLOW reported, it gets 0/128, with -EPIPE. And the recovery got a bit confused; it's a STALL but not from the device, it's from the hub.
It might be worth making EHCI use a different code in that case, if this class of TT-related errors starts to be trouble.
Again, this case worked fine with the sd.c changes, so it does seem to be all related to "big" transfers out of the mode page.
Or at any rate, "big enough" to confuse the device.
Thanks for the additional test results.
- Dave
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
