From: Stefan Smietanowski <stesmi@stesmi.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net, MCU.Tools@silabs.com
Subject: Re: Linux support for SiLabs CP210x devices
Date: Wed, 18 May 2005 20:00:05 +0200 [thread overview]
Message-ID: <428B82A5.6080705@stesmi.com> (raw)
In-Reply-To: <20050518155815.GA16544@kroah.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Greg.
> Back in November of last year, I wrote about how SiLabs were
> distributing a binary only version of a usb-serial driver for Linux that
> was violating the GPL <http://thread.gmane.org/gmane.linux.kernel/256403>
>
> Well, it looks like SiLabs and MCCI have finally released the source
> code to their driver, but in obfuscated form. I've attached the .zip
> file to this message so that everyone can see this horrible nightmare of
> a "driver". As per the GPL, they are still violating the license as
> obfuscated code releases is not allowed. And as such, they are still
> violating my copyright, and the copyrights of a few other kernel
> developers.
>
> So, just to re-iterate, I very soundly do not recommend ever buying any
> devices from this company, as if this is the way they treat well
> established legal issues, who know what else they have done...
>
> Oh, and if you don't want to go through the trouble of opening up the
> zip file, I've included inline their header file, in all of it's glory,
> with no changes made by me at all, below.
>
> And yes, if you notice the 2.6 kernel does now support this device, but
> that is because of some people reverse engineering the device. It was
> by no help of the company involved (when seeing this code, those
> developers just laughed and said it would be more work to try to read it
> than to finish up the driver itself.)
Is this for real? What exactly do they think they're trying to pull
here?
I've seen borderline violations but this .. this .. this ..
If the .h file was bad, the .c's are worse.
// Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFCi4KkBrn2kJu9P78RAum2AJ9ead+TvBLTbPVW2gvfUXFlY/9cGwCfWmud
Trfomjn4d+Wd1HHw/IAdlvQ=
=WWVK
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-05-18 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 17:39 Linux support for SiLabs CP2102 devices Greg KH
2004-11-18 19:41 ` [linux-usb-devel] " Marr
2005-05-18 15:58 ` Linux support for SiLabs CP210x devices Greg KH
2005-05-18 18:00 ` Stefan Smietanowski [this message]
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=428B82A5.6080705@stesmi.com \
--to=stesmi@stesmi.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;
as well as URLs for NNTP newsgroup(s).