linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.de>
To: "Steven J. Ackerman" <steve@acscontrol.com>
Cc: "'Bjørn Mork'" <bjorn@mork.no>,
	linux-usb@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: Linux USB Serial
Date: Tue, 18 Sep 2012 08:46:10 +0200	[thread overview]
Message-ID: <5789366.GGq3fAeCyr@linux-lqwf.site> (raw)
In-Reply-To: <00b801cd9518$715dd160$54197420$@acscontrol.com>

On Monday 17 September 2012 17:07:26 Steven J. Ackerman wrote:
> Bjrn-
> 
> Thank you for your response.
> 
> This change gets me closer. I can now successfully execute the modprobe
> without error, but the device still doesn't show up in /dev/ttyUSB? .

It shouldn't. Your device follows the CDC ACM specification, aside from
the incorrect subclass. Such devices don't generate /dev/ttyUSB devices
nodes. They generate /dev/ttyACM nodes.

> sja@UBUNTU-10:~$ sudo modprobe usbserial vendor=0x0c6a product=0x0005

That is the wrong driver. usbserial is for vendor specific serial devices.
Your device follows a class specification. You need cdc_acm. As soon
as the subclass is fixed, it should autoload.

If cdc_acm doesn't bind, please post "dmesg".

	Regards
		Oliver


  parent reply	other threads:[~2012-09-18  6:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17 19:28 Linux USB Serial Steven J. Ackerman
2012-09-17 20:07 ` Bjørn Mork
2012-09-17 21:07   ` Steven J. Ackerman
2012-09-17 21:41     ` Greg KH
2012-09-17 21:56       ` Steven J. Ackerman
2012-09-17 22:08         ` 'Greg KH'
2012-09-17 22:27           ` Steven J. Ackerman
2012-09-18  6:46     ` Oliver Neukum [this message]
     [not found]       ` <5789366.GGq3fAeCyr-ugxBuEnWX9yG/4A2pS7c2Q@public.gmane.org>
2012-09-18 14:00         ` Steven J. Ackerman

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=5789366.GGq3fAeCyr@linux-lqwf.site \
    --to=oneukum@suse.de \
    --cc=bjorn@mork.no \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=steve@acscontrol.com \
    /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).