mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marr <marr@flex.com>
To: Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Cc: MCU.Tools@silabs.com
Subject: Re: [linux-usb-devel] Linux support for SiLabs CP2102 devices
Date: Thu, 18 Nov 2004 15:41:40 -0400	[thread overview]
Message-ID: <200411181441.40458.marr@flex.com> (raw)
In-Reply-To: <20041118173908.GA10667@kroah.com>

On Thursday 18 November 2004 12:39pm, Greg KH wrote:
> Hi all,
>
> I've been getting a lot of requests lately to see if Linux supports the
> USB to serial device from Silicon Laboratories called the CP2102 chip.
> It turns out that the company is claiming Linux support, yet they are
> only shipping a binary driver for Red Hat Linux 9.0.
>
> In talking with the company, they insist that they will not release the
> source code to this module, and they claim that they are not infringing
> on any rights by not doing so.

(... snip ...)

> So, they are in violation, so what.  Well, I can't do much about this
> (due to my employer's rules about suing companies).  But I can do my
> best to spread the word that the CP2102 device is not supported on
> Linux, and should be avoided at all costs by anyone considering such a
> device in a future design.  I encourage everyone else to help spread
> this information too.

(... snip ...)

> So, in conclusion, please stay away from Silicon Laboratories devices,
> if you want to run Linux, as they are obviously not supporting Linux in
> any way.

If anyone has the USB Vendor/Product IDs (VID/PID) for these errant devices, a 
negative report (maybe including a link back to Greg's post in the 
Linux-USB-Devel list archives [http://
marc.theaimsgroup.com/?l=linux-usb-devel&m=110079963113076&w=2]) should be 
submitted to the USB 'Working Devices' list for RS-232/USB adapters at:

   http://www.qbik.ch/usb/devices/showdevcat.php?id=12

(I just did a search at that location for 'CP2102' and 'Silicon' and 'SiLabs' 
and found no entries for any such devices. I don't see any USB VID/PID info 
about them or their devices in the 'usb.ids' file either.)

That might help keep future users away from the devices of a company with such 
a poorly-thought-out policy.

Thank you, Greg, for alerting us to this situation.

Bill Marr


  reply	other threads:[~2004-11-18 19:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 17:39 Greg KH
2004-11-18 19:41 ` Marr [this message]
2005-05-18 15:58 ` Linux support for SiLabs CP210x devices Greg KH
2005-05-18 18:00   ` Stefan Smietanowski
2005-05-18 18:28     ` Greg KH

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=200411181441.40458.marr@flex.com \
    --to=marr@flex.com \
    --cc=MCU.Tools@silabs.com \
    --cc=greg@kroah.com \
    --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

Powered by JetHome