public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Nemosoft Unv." <nemosoft@smcc.demon.nl>
Cc: Greg Kroah <greg@kroah.com>,
	luc@saillard.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: The return of PWC
Date: Mon, 02 May 2005 18:45:02 +0100	[thread overview]
Message-ID: <1115055898.10369.30.camel@localhost.localdomain> (raw)
In-Reply-To: <200505020229.35129@smcc.demon.nl>

On Llu, 2005-05-02 at 01:29, Nemosoft Unv. wrote:
> In case you hadn't noticed, that code has been reverse compiled (I would not 
> even call it "reverse engineered"), and is simply illegal. Maybe not in 
> every country, but certainly in some. There are still some intellectual 
> property rights being violated here, you know, and I'm surprised at the 
> contempt you and Linux kernel maintainers show in this regard for a few 
> lines of the law.

Reverse engineering in the EU for compatibility is legal. It was done in
the EU. Linux exists because the law is sensible and allows such
actions, its the same reason you aren't still buying all your flush
toilets from Thomas Crapper & Son.

> Now don't get started on "it was GPL code before you left bla bla" or "you 
> should not have abonded the project bla bla blah" and "this court here has 
> ruled reverse engineering is allowed and so on mumble mumble". 

Don't like facts ? The legal position on reverse engineering is in
general fairly clear. What you describe might not be. If so then we need
to find someone who hasn't read the code to rewrite it from the
algorithm description of the current code. Shouldn't take more than a
week.

[Its the difference between disassembling the code and publishing a form
of the disassembly and writing a new implementation of the algorithm.
One is copyright violation the other is reverse engineering]

> Anyway, I'll inform my contacts at Philips tomorrow. I don't know how they 
> will react; maybe they'll go nuts, maybe they'll let it pass quitely; it's 

I *am* concerned by your comments about how the reverse work may have
been done, and whether proper process was followed. I'd be greatful if
you would forward me your contact at Philips too. You are considered as
having an axe to grind and I'd rather discussion occurred between
Philips and the Linux community than via yourself.

You've also said yourself that the NDA you had was expired so the
previous lack of a GPL module is your personal agenda and nothing to do
with anyone else. That makes me wonder what your real goal is.

Alan


  parent reply	other threads:[~2005-05-02 17:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02  0:29 The return of PWC Nemosoft Unv.
2005-05-02 16:02 ` Greg KH
2005-05-02 17:45 ` Alan Cox [this message]
2005-05-04  3:27 ` Rob van Nieuwkerk
2005-05-09 16:31   ` Alan Cox

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=1115055898.10369.30.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc@saillard.org \
    --cc=nemosoft@smcc.demon.nl \
    /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