From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] usb serial on raspberry pi (again)
Date: Thu, 15 Dec 2016 11:15:48 +0000 [thread overview]
Message-ID: <9d3492c0b883d8c6d0c83b0de2e20b85@quintile.net> (raw)
In-Reply-To: <ad419cd19f59ede0739d39e840a70e12@hamnavoe.com>
Hi,
I have tried the usb->serial adapters I could find lying around the office.
Using the code you sent me, not the very latest from sources.
The FTDI chips we use in our products work fine
ep13.0 255 csp 0x0000ff vid 0x10c4 did 0xea60 'Silicon Labs' 'CP2102 USB to UART Bridge Controller' dwcotg
These are Silabs cp2102 (https://www.silabs.com/Support%20Documents/TechnicalDocs/CP2102-9.pdf)
A cheap chinese, no-name FTDI adapter also works nicely
255 csp 0xffffff vid 0x0403 did 0x6001 FTDI 'USB Serial Converter' dwcotg
I have a "Ugreen" branded prolific usb/serial adapter which also works, it is not autodetected
but running usb/serial creates and endpoint which works.
ep12.0 255 csp 0x0000ff vid 0x067b did 0x2303 none <nil> dwcotg
I also have a dual channel prolific adapter and this doesn't work but I couldn't make it work with
windows either so its either very strange or baybe its just fried.
ep6.0 hub csp 0x000009 ports 4 none <nil> dwcotg
ep12.0 hub csp 0x000009 ports 4 none <nil> dwcotg
My USB network adapter is a KY-88772a (https://i.ytimg.com/vi/Hcy5f9c2TXE/maxresdefault.jpg)
which works quite well but seems to get confused somtimes and needs to be reset.
I have not worked out what provokes it but I think (educated guess only) entering
promiscuous mode makes it unhappy.
Thanks very much for all your help,
-Steve
next prev parent reply other threads:[~2016-12-15 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 10:44 Richard Miller
2016-12-15 11:15 ` Steve Simon [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-27 10:40 Steve Simon
2016-12-12 20:33 ` Richard Miller
2016-12-12 20:39 ` Richard Miller
2016-12-13 10:06 ` Gorka Guardiola
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=9d3492c0b883d8c6d0c83b0de2e20b85@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.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).