All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Cc: MCU.Tools@silabs.com, grayson@caltech.edu, jan@pololu.com,
	karl@accusense.com
Subject: Linux support for SiLabs CP2102 devices
Date: Thu, 18 Nov 2004 11:28:59 -0800	[thread overview]
Message-ID: <20041118192859.GA29395@kroah.com> (raw)

(resent without tarball to let lkml filters accept it.)

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.  I claim that this is not true, as to
write a usb to serial driver for Linux you have to use the
drivers/usb/serial/usb-serial.h header file which is specifically
licensed under the GPL v2.  This file contains inline functions and
structures that all usb-serial drivers need to use in order to work
properly.

In short, there's no way you can write a Linux usb-serial driver, that
uses the usbserial interface, without it being a derived work of other,
GPL only code.

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.

If people are looking for a good usb to serial chip that is supported on
Linux, Windows, and OS-X, there's the PL2303 device from Prolific, and
the FTDI-SIO chip, and the MCT-U232 chip.  All of these work very well
on Linux, and are fully supported by all distros.  I think they even
might be cheaper than the CP2102 device too :)

Oh, and just for fun, the Linux driver that SiLabs is distributing is
availble:
	http://marc.theaimsgroup.com/?l=linux-usb-devel&m=110079963113076&q=p3
if anyone wants to poke around in it.  The tarball contains 2 binary
drivers, one of them a version of the usbserial.c file (which plainly is
licensed under the GPL) and a mcci_usb.o binary driver.  Have fun with
it, but don't blame me for any badness that might happen to your box for
running it, no one has any way of knowing exactly what this driver is
doing.

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.

thanks,

greg k-h

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 19:28 Greg KH [this message]
     [not found] <mailman.1100831940.24470.linux-kernel2news@redhat.com>
2004-11-20  0:22 ` Linux support for SiLabs CP2102 devices Pete Zaitcev
2004-11-20  0:27   ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2004-11-18 17:39 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=20041118192859.GA29395@kroah.com \
    --to=greg@kroah.com \
    --cc=MCU.Tools@silabs.com \
    --cc=grayson@caltech.edu \
    --cc=jan@pololu.com \
    --cc=karl@accusense.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.