Matthew Dharm wrote:
Does anyone besides me find it a bit odd that we bind drivers to an interface, yet need to pass the device pointer to functions like usb_control_msg()?
And meanwhile, all the I/O is really directed to endpoints ... ;)
For ep0 at least we have the excuse that we'd have to craft our own endpoint descriptor ... it's shared between all interfaces, and is a special case in a lot of ways. (Usable before device is configured, and even before it's addressed.) For all other endpoints in the currently active configuration (including interface settings) it's always seemed odd that the current API takes such a roundabout way to get to core "queue a request to this endpoint" logic. The usb_submit_urb() code could (should!) involve a lot less overhead. You may recall that I posted a draft of device-side "gadget" API where I/O (except control traffic) was focussed on the endpoints, not devices or interfaces, for such reasons. I'll post an update on that before too long, with working code. Such I/O calls _could_ work on the host side too (2.7 issue). - Dave ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
