> This sounds like exactly what I want.  Perhaps waiting for shared-code
> merging will bring about everything I'd like to see....

That'd be nice!  Or use it with EHCI before other hcds start to use
the "sharable" code.  I saw a high speed CD-RW on the web...


> Thus, if I was writing and my bulk out endpoint STALLed, then yes, I want
> the string of bulk-out transfers to all fail with -EPIPE.  However, if
> there is a bulk-in transfer in the chain, why not do it?

Because that IN only makes sense if the OUT succeeded!

>      Better yet, if
> there is a CLEAR_HALT in the chain, execute that too, and then everything
> after that will be fine.

Why not do that only when the OUT bulk chain failed with EPIPE? :)

On error, the little queueing engine could chase "urb->alt_next"
instead of "urb->next" ... if completion functions aren't wanted.

- Dave




_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to