The inverval parameter in the urb: Does it work for all combinations of IRQ and ISO with uhci,usb-uhci and ehci?
Sounds like you're thinking 2.4. Basically on 2.4 the iso period must be 1 frame, and interrupt periods must be some 2^N frames (N>0), but they should work otherwise. On 2.6 the restrictions are loosened but you'll need to use urb queueing to get short periods.
A similar question regarding the conext field in the urb: Is it cleared by any driver during an unlink? Do I have to fill the field when I want to restart the periodic transfer? I don't mean resubmit in the irq-handler. I mean when I want to resume the transfer later after an unlink.
The context field is owned purely by the usb device driver; usbcore and hcds won't even look at it.
- Dave
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
