public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: Michael Poole <mdpoole@troilus.org>
Cc: hch@lst.de, linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: more files with licenses that aren't GPL-compatible
Date: Thu, 17 Jun 2004 10:09:30 -0700	[thread overview]
Message-ID: <20040617100930.A9108@adam> (raw)
In-Reply-To: <87n032xk82.fsf@sanosuke.troilus.org>; from mdpoole@troilus.org on Thu, Jun 17, 2004 at 11:44:29AM -0400

On Thu, Jun 17, 2004 at 11:44:29AM -0400, Michael Poole wrote:
> The first "official" version of Linux that included USB serial code
> that mentioned you (Adam Richter and/or Yggdrasil) was 2.4.  That same
> version included the same binary firmware you complained about in
> 2001, and the changelog in usbserial.c makes it clear that *at least*
> the WhiteHEAT firmware was already present when you contributed your
> code.
> 
> Would you explain why your claim of copyright infringement is not
> estopped by the pre-existing condition of firmware being present?

	Why would it be, and what kind of stopping ("estoppel")
are you referring to?

	I do not believe that when one contributes to Linux that
one is promising not to pursue other copyright problems anywhere
elsewhere in the code.  If you can point to a court decision or law
that says something analogous, I would be interesting in hearing
about it.

	I believe the pre-exising condition, if it was pre-existing,
of the firmware being present in a few infringing drivers among many
non-infringing drivers would not mean that permission was granted
to produce a derivative work comingling the few illegal drivers
(or even prove prior knowledge of the few illegal drivers).

	I know I have been complaining about the infringing drivers
and asking that people stop infringing approximately since I became
aware of the infringement.

	Again, I'm not a lawyer, so please do not use my layman's
opinions as legal advice.

-- 
                    __     ______________
Adam J. Richter        \ /
adam@yggdrasil.com      | g g d r a s i l

  reply	other threads:[~2004-06-17 18:19 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18  6:29 more files with licenses that aren't GPL-compatible Adam J. Richter
2004-06-17 15:44 ` Michael Poole
2004-06-17 17:09   ` Adam J. Richter [this message]
2004-06-17 19:14     ` Kyle Moffett
2004-06-17 20:51       ` Flavio Stanchina
2004-06-17 20:53         ` Kyle Moffett
2004-06-17 21:05         ` mdpoole
2004-06-17 21:10           ` Christoph Hellwig
2004-06-17 21:45           ` Flavio Stanchina
2004-06-17 20:22     ` mdpoole
2004-06-17 18:05 ` Greg KH
2004-06-17 19:54   ` Christoph Hellwig
2004-06-17 20:22     ` Greg KH
2004-06-17 20:30       ` Christoph Hellwig
2004-06-17 20:52         ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2004-06-18  6:56 Adam J. Richter
2004-06-18 11:09 ` mdpoole
2004-06-16 23:47 Wichmann, Mats D
2004-06-17  1:18 ` Kyle Moffett
2004-06-15 20:57 Christoph Hellwig
2004-06-16  0:38 ` Eric
2004-06-16  1:27   ` Kyle Moffett
2004-06-16  4:11   ` David Schwartz
2004-06-16 20:34     ` Erik Harrison
2004-06-16 20:37       ` Christoph Hellwig
2004-06-16 21:21       ` David Schwartz
2004-06-16 22:45         ` Oliver Neukum
2004-06-16 23:45           ` David Schwartz
2004-06-17 14:09             ` Timothy Miller
2004-06-17 18:35               ` David Schwartz
2004-06-17 19:22                 ` Timothy Miller
2004-06-17  7:59           ` Christoph Hellwig
2004-06-17  8:43             ` Oliver Neukum
2004-06-17  8:47               ` Christoph Hellwig
2004-06-17 10:09             ` Martin Diehl
2004-06-17 10:14               ` Christoph Hellwig
2004-06-19 18:29               ` David Woodhouse
2004-06-17 14:04           ` Timothy Miller
2004-06-16 22:49       ` Helge Hafting
2004-06-18  9:08         ` Adrian Cox
2004-06-18 11:21           ` Kyle Moffett

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=20040617100930.A9108@adam \
    --to=adam@yggdrasil.com \
    --cc=greg@kroah.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdpoole@troilus.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