linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Steven J. Ackerman" <steve-I01wfHm1r9xGyKhy+UYuEA@public.gmane.org>
To: 'Oliver Neukum' <oneukum-l3A5Bk7waGM@public.gmane.org>
Cc: "'Bjørn Mork'" <bjorn-yOkvZcmFvRU@public.gmane.org>,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: Linux USB Serial
Date: Tue, 18 Sep 2012 10:00:11 -0400	[thread overview]
Message-ID: <002e01cd95a5$ec0a4190$c41ec4b0$@acscontrol.com> (raw)
In-Reply-To: <5789366.GGq3fAeCyr-ugxBuEnWX9yG/4A2pS7c2Q@public.gmane.org>

> 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.
> 

Thank you.  I did some more research on this last night and found out that 
I was being mis-lead by observing how other USB Serial devices were 
working and used under Linux - without having to install a driver.
Apparently 
these were all using the FTDI chip - and there is a driver that is already 
installed for them.

> 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.
> 

Yes - the driver now autoloads and I can communicate with the device 
using the /dev/ttyACM0 node. I was able to install picocom and talk to and 
from our display.

Thanks to everyone who replied to this question for your assistance.

Steven J. Ackerman, Consultant
ACS, Sarasota, FL
http://www.acscontrol.com
mailto:steve-I01wfHm1r9xGyKhy+UYuEA@public.gmane.org





--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2012-09-18 14:00 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
     [not found]       ` <5789366.GGq3fAeCyr-ugxBuEnWX9yG/4A2pS7c2Q@public.gmane.org>
2012-09-18 14:00         ` Steven J. Ackerman [this message]

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='002e01cd95a5$ec0a4190$c41ec4b0$@acscontrol.com' \
    --to=steve-i01wfhm1r9xgykhy+uyuea@public.gmane.org \
    --cc=bjorn-yOkvZcmFvRU@public.gmane.org \
    --cc=linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=oneukum-l3A5Bk7waGM@public.gmane.org \
    /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).