From: David Brownell <david-b@pacbell.net>
To: Peter Matthias <espi@epost.de>, linux-kernel@vger.kernel.org
Cc: linux-usb-devel@lists.sourceforge.net
Subject: Re: ACM USB modem on Kernel 2.6.0-test
Date: Sat, 11 Oct 2003 11:53:27 -0700 [thread overview]
Message-ID: <3F8851A7.3000105@pacbell.net> (raw)
> usb 3-3: configuration #1 chosen from 2 choices
> drivers/usb/class/cdc-acm.c: need inactive config #2
> drivers/usb/class/cdc-acm.c: need inactive config #2
Until we get more intelligence somewhere, do this:
# cd /sys/bus/usb/devices/3-3
# echo '2' > bConfigurationValue
#
That makes the device use vendor-neutral protocols
to talk to the host, not MSFT-proprietary ones. (It's
important to use the numbers from those messages; they
will change if you use different USB ports.)
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.
- Dave
next reply other threads:[~2003-10-11 18:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-11 18:53 David Brownell [this message]
2003-10-12 12:07 ` ACM USB modem on Kernel 2.6.0-test Jamie Lokier
2003-10-12 18:59 ` David Brownell
2003-10-17 20:04 ` David Brownell
2003-10-19 15:13 ` David Brownell
[not found] <FJVJ.4PN.5@gated-at.bofh.it>
[not found] ` <I1Yg.6oy.13@gated-at.bofh.it>
[not found] ` <I1Yg.6oy.11@gated-at.bofh.it>
2003-10-19 9:34 ` Peter Matthias
[not found] <FwYB.Z9.25@gated-at.bofh.it>
2003-10-12 8:40 ` Peter Matthias
2003-10-12 12:06 ` Jamie Lokier
2003-10-12 17:52 ` Peter Matthias
2003-10-13 16:28 ` Peter Matthias
[not found] ` <HJ5m.2Eb.23@gated-at.bofh.it>
2003-10-18 16:21 ` Peter Matthias
[not found] ` <Inm6.60T.19@gated-at.bofh.it>
2003-10-20 16:54 ` Peter Matthias
-- strict thread matches above, loose matches on Subject: below --
2003-10-11 12:38 Peter Matthias
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F8851A7.3000105@pacbell.net \
--to=david-b@pacbell.net \
--cc=espi@epost.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).