mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: FD Cami <francois.cami@free.fr>
To: Jo Shields <directhex@apebox.org>
Cc: linux-kernel@vger.kernel.org, legal@narasimha.gpl-violations.org
Subject: Re: GPL Violation: Compro Technology Inc, 2.6.17 modified binary-only kernel distribution
Date: Sat, 17 May 2008 00:32:06 +0200	[thread overview]
Message-ID: <20080517003206.25e90937@olorin> (raw)
In-Reply-To: <1210975212.7181.26.camel@mortos>


(adding gpl-violations.org in CC)

--
fdc


On Fri, 16 May 2008 23:00:12 +0100
Jo Shields <directhex@apebox.org> wrote:

> Hi,
> 
> I've discovered a GPL violation by Taiwanese TV card manufacturer Compro
> Technology.
> 
> On their site, they are offering a "driver" for Mandriva
> Linux 2007.1, in the form of an 18 meg "linux.rpm"[1,2,3,4]. This
> "driver" is, in fact, an entire kernel image (from snd-emu10k1.ko to
> libata.ko, with everything in between), generated from Mandriva's kernel
> source package, with local modifications to at least two files (major
> file size gap between Compro and Mandriva kernels in tuner.ko and
> cx88xx.ko).
> 
> Their "driver" is being offered in binary-only form, without any
> accompanying license, and I have received no replies to a formal request
> for source after 2 (Taiwanese) working days. Obviously, this violates
> several GPL clauses, and infringes on the rights of every kernel
> developer with code in 2.6.17.
> 
> It is also the opinion of a LinuxTV developer with whom I've been
> discussing the matter that their modified drivers appear to contain
> large un-redistributable portions of code from a chip vendor's
> proprietary SDK, but we obviously can't adequately check this with
> only .ko files to work with.
> 
> They appear to be offering a similar "driver" for Fedora Core 6, which
> is non-functional, presumably due to a failed upload (cpio fails to
> extract the rpm)[4,5].
> 
> I'm not 100% certain what my next step should be, so I decided this was
> the best place to give a public airing. One suggestion I've had
> suggested is to file a DMCA takedown notice with their (US-based) ISP,
> but I've no idea whether it's the right stage to do something like that,
> nor do I have any claim to any code contained in the kernel. At any
> rate, I wanted to make the kernel developers informed of this discovery.
> 
> I'm not on this mailing list, so a CC: would be appreciated.
> 
> --Jo Shields
> 
> 
> [1] http://www.comprousa.com/downloadfiles/linux.rpm
> [2] http://www.comprousa.com/en/download/sseries.html
> [3] http://www.comprousa.com/en/download/tseries.html
> [4] http://www.comprousa.com/en/download/xseries.html
> [5] http://www.comprousa.com/downloadfiles/kernel-2618prep-3i386.rpm
> 

  reply	other threads:[~2008-05-16 22:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 22:00 Jo Shields
2008-05-16 22:32 ` FD Cami [this message]
2008-05-29 13:21   ` Jo Shields
2008-05-30  3:49     ` David Newall
2008-05-30  7:33       ` Jo Shields
2008-05-30  8:30     ` Bernd Petrovitsch
2008-05-30 21:01       ` Alexandre Oliva

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=20080517003206.25e90937@olorin \
    --to=francois.cami@free.fr \
    --cc=directhex@apebox.org \
    --cc=legal@narasimha.gpl-violations.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®