Oliver Neukum wrote:
But we don't really _have_ to keep track of all of them, right? And it
Someone needs to, but it doesn't need to be the device driver. The
current approach has "hcd.c" do it, part of usbcore.
A part that doesn't need to be used. It's a little late to break all the
little HCDs, isn't it?
HCDs that track urbs internally would still be usable. Just one
more update for the 2.6 series kernel would hardly "break" them.
Secondly, if I understand the code correctly, it keeps per device lists.
That's not enough. The lists must be per interface, think configuration
changes.
A per-device list is sufficient, and a lot cheaper to maintain.
Doing it per-interface would add work to the submit path that's
hardly ever needed ... better to have that work delayed until
it's actually needed.
- Dave
-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
