> I adding printing out of the td_flags, and it seems that every > time > that it gets the condition code of 0xA (which is reserved in the > OHCI spec, but is defined as TD_BUSY in ohci-isp1362-emu.c), it > gets stuck in this loop. > > So it seems that it doesn't handle the busy condition. It looks > like the code just keeps on retrying, but something needs to be > done to get it out of this state. >
If I can just add to this observation.. It seems that right before my situation, there's a TD / PTD that isn't being processed correctly. In every case where we read 72 bytes, we read 8 bytes right afterwards, except this one. For every TD handled, except for this last one, we get something similar to: Retiring TD c1092000 ED c10f2040 info 00400982 with CC=0 #b8ad finish_xfer: PTD 0610 of TD c1092000 finished #b8ad I'm trying to find out why this is happening, but let me know if you figure this out before I do. (Also, I'd prefer to fix any timing problems rather than work-around them) Thanks yet again, Mike ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
