From: Alan Stern [mailto:[EMAIL PROTECTED] 
> If there's anything in particular you need to know or are 
> interested in, I 
> might be able to help.  Bear in mind that the 2.4 drivers are 
> much more 
> complicated and much less reliable than the 2.6 driver.

Thanks, I appreciate it. So...

Why doesn't queueing work?

Rhetorical mostly, :-) but if you happen to have an answer, I'm
willing to make a patch.

The only guess I was able to come up with is that there's a race
between uhci_submit_urb() and its callees uhci_submit_bulk() &
uhci_append_queued_urb() and uhci_interrupt() and its callees that
causes the "Chain of QHs and TDs" to be such that the hardware thinks
the chain is done, but that the driver things the chain is running.

I did see that uhci_interrupt() stops entering ie interrupts have
stopped being generated, but not due to lockup since the system was
fine, and I could reload my driver and have it communicate again.

Please don't spend any time on this on my behalf; I've already worked
around it.

..Stu



-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to