On Sun, 1 Feb 2004, Guennadi Liakhovetski wrote: > On Sun, 1 Feb 2004, Alan Stern wrote: > > > The patch below is nearly the same as the last one, and you should test it > > in the same way. What's new about it is that it prints out the values > > stored in the "terminating TD". That's the Transaction Descriptor at the > > end of the USB schedule, and it's the one that set_next_interrupt relies > > on to actually cause an interrupt request. > > Ok, you asked for it - it is below. But I guess, it is going to disappoint > you - those TDs are exactly the same before and after the error. If I read > it right.
It's not a disappointment -- it indicates that the TD isn't getting messed up, so the problem must lie in the controller itself. In other words, the hardware seems to be misbehaving. I say "seems to be" because I'm still not entirely certain that it isn't an error in the driver causing this, but it's pretty hard to see how it could be. I'll probably have to get some advice on how to attack this. More later... Alan Stern ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
