Alan Stern wrote:
Actually in that case your "just wait for urb completion" model wouldI believe, as a result of a somewhat hasty perusal of the USB spec, that it is legal under some circumstances for a device to fail to reply at all to a USB transaction for an extended period of time. For instance, if several isochronous OUT transfers in a row get corrupted, the device is not obliged to transmit a handshake or any other kind of reply. Unless the HCD includes some provision for timing out a TD/ED, it would not notice anything wrong.
eventually work, since the ISO transfers are all "fire and forget".
There are no retries for ISO.
- Dave
-------------------------------------------------------
This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at:
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
