Jamie Lokier wrote:
David Brownell wrote:

Hmm ... maybe usbcore would be better off with a less
naive algorithm for choosing defaults.  Like, preferring
configurations without proprietary device protocols.
That'd solve every cdc-acm case, and likely others.


Presumably 2.4 does that, because my acm modem works with 2.3 and 2.4
kernels.

No, 2.4 is just as dumb -- but it had a way to kluge around that. But that kluge doesn't work any more on 2.6, mostly because usb_set_configuration() now behaves sanely. (Not only does it shut down the old configuration ... but it also sets up the new one correctly.)

Your modem should work just fine with 2.6 too, if you just
switch to the other configuration from userspace.  However,
I'd certainly like to reduce the need for such steps.


Do you know anything about the proprietary protocols, btw?

My understanding is that knowing technical details involves signing NDAs with MSFT. But I've not investigated much; likely other people know more.

- Dave





-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to