From: amadeus84@verizon.net (Amadeus W.M.)
To: kernelnewbies@lists.kernelnewbies.org
Subject: usb serial programming
Date: Mon, 21 Jul 2014 19:25:24 +0000 (UTC) [thread overview]
Message-ID: <pan.2014.07.21.19.25.24@verizon.net> (raw)
In-Reply-To: 20140721190643.GA13587@kroah.com
>
> What is the:
> Bus 004 Device 008: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
>
> device?
That's my backup power supply.
>
>> Should /dev/ttyUSB0 pop up when I plug the adapter into the usb port,
>> even before I connect anything to the serial port of the cable?
>
> Yes.
>
> What happens in the kernel log when you plug the device into the system?
>
> Try doing:
> dmesg -c
> # plug in the adapter now
> dmesg
> to just see the log messages for that, and not the whole kernel boot
> log.
>
2) root:~> dmesg -c #plug-in adapter
3) root:~> dmesg
Absolutely nothing. I also did
tail -f /var/log/messages
then plugged in the adapter, and again, everything seems dead. The USB port
is ok, because other devices (e.g. the Fushicai video grabber) do work.
>> If the adapter is not supported, can I write a driver for it? I'll be happy to,
>> with a little guidance to get me started. Any pointers?
>
> Odds are the device id just needs to be added to an existing driver as
> I do not know of any "new" usb-serial converter chips that Linux does
> not already support.
>
Oh, one more thing. Reading about these converters, I saw many use an
ftdi chip, so I did modprobed ftdi_elan and ftdi_sio:
7) root:~> lsmod | grep ftdi
ftdi_elan 36689 0
ftdi_sio 48770 0
In fact, the dmesg above was with the ftdi modules loaded.
next prev parent reply other threads:[~2014-07-21 19:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 3:19 usb serial programming Amadeus W.M.
2014-07-21 18:18 ` Greg KH
2014-07-21 18:27 ` Bruce Rowen
2014-07-21 19:05 ` Amadeus W.M.
2014-07-21 19:42 ` Bruce Rowen
2014-07-21 18:55 ` Amadeus W.M.
2014-07-21 19:06 ` Greg KH
2014-07-21 19:25 ` Amadeus W.M. [this message]
2014-07-21 19:46 ` Greg KH
2014-07-23 0:26 ` Amadeus W.M.
2014-07-22 5:12 ` Sudip Mukherjee
2014-07-23 0:29 ` Amadeus W.M.
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=pan.2014.07.21.19.25.24@verizon.net \
--to=amadeus84@verizon.net \
--cc=kernelnewbies@lists.kernelnewbies.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).