> So I have set up a periodic INT transfer, but was not able to modify
> the transfer size from inside the completion handler.
> 
> IMO this asymmetric behavior of the INT transfer is a design weakness.
> Maybe it should be addressed in 2.5.x ?

What's the asymmetry?  You've submitted an INT transfer for
N bytes, and each time that's what's attempted.  OUT and IN
work the same.

Or are you referring to the inability to change the transfer size?
That would only be necessary on OUT transfers ... :)  I might
agree that INT-OUT needs some work.


> So I have tried to use one-shot-INT transfers. The first thing I have noticed
> is that is is not possible to submit the next transfer from the completion
> handler of the previous one.

That seems buglike to me.  On the other hand, I don't recall 
one-shot interrupt transfers getting specified and then added
to the API.

I'd suggest you just unlink the interrupt urb in your completion
handler and then submit a new one when the unlink completion
is reported, but unfortunately that wedges usb-uhci...

- Dave




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

Reply via email to