The transfer mode is isochronous.
Which is probably part of the reason for the crash; that code has hardly been used, and there are no tests to make sure that it works right either..
Related to this problem: how often is the completion routine called? Every microframe (125us) in high speed? Does urb->interval control this?
For high speed isochronous submissions, urb->interval is in microframes; and each packet in the URB is issued at that interval. When all of the packets have been transferred (possibly with errors), the urb's completion handler gets called.
What I find also irritating that the ehci scheduler needs an interval for ISO transfer although this is only needed for int endpoints. At least this says the documentation when I look at usb.h.
Erm, then the doc is wrong. You might be looking at the 2.4 code, where for some odd reason there was an assumption that the only legal ISO period was once every uframe. USB is specified otherwise.
- 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/345/0 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
