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? Is the interval always determined from the device descriptor data? If so then why doesn't some lower level code do that and relieve all drivers of that task? Do other drivers set interval? How? I have looked around the code a bit and mostly see reading of interval, or setting it to 1. rtl8150 does set it to 100ms. Is this what the descriptor says too? -- Don Reid ------------------------------------------------------- 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
