I have thought some more about setting the interval (for ISO & INTR urbs) in devio. Yes this is currently needed. But does it make sense for this to be set in devio?
It seems to me (who knows little about the structure or history of the Linux USB drivers) that this is would be a common function done at some lower level (in hcd?). I don't mean just the conversion from the encoded form to an integer (which could be in a macro). Why does the higher level driver devio even have to set interval?
Because historically drivers needed the option of ignoring the policy set in braindead device descriptors, to use a better transfer period. Example, low speed devices specifying 1 msec intervals likely waste rather huge chunks of bandwidth ... best to force larger intervals, like 8 or 16 msec.
However the usbfs code (devio) didn't support that mechanism; there's no way to pass the transfer period down.
- Dave
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
