From: mdpoole@troilus.org
To: "Adam J. Richter" <adam@yggdrasil.com>
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 16:22:42 -0400 [thread overview]
Message-ID: <87isdqx7cd.fsf@sanosuke.troilus.org> (raw)
In-Reply-To: <20040617100930.A9108@adam> (Adam J. Richter's message of "Thu, 17 Jun 2004 10:09:30 -0700")
Adam J. Richter writes:
> 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?
[snip]
>From what I can see, the USB serial drivers included firmware images
before you contributed to that code. If you contributed changes with
reckless disregard to their presence (i.e. should have known they were
there and you did not say "I contribute this on the condition that the
maintainers work to remove binary firmware"), I believe that you
accepted their presence.
http://www.ipwatchdog.com/equitable_estoppel.html discusses equitable
estoppel vis-a-vis patent rights (which are treated similarly to
copyrights by many courts). When you contributed your changes to the
USB maintainers, they -- and later redistributors -- inferred that you
would not allege copyright infringement by applying your changes to
the kernel that existed then.
The first binary firmware I found in the kernel was included in linux
2.0, released in June 1996. There might be an earlier case. You
might argue plausible ignorance of that particular driver, but you as
an individual have a harder claim to demonstrate. See below.
> I know I have been complaining about the infringing drivers
> and asking that people stop infringing approximately since I became
> aware of the infringement.
You managed to contribute some significant creative (copyrightable)
change to the USB serial code without noticing that *a quarter* of the
files in that directory were headers that defined firmware? I do not
know if a court would take such a claim seriously, but as a software
developer, I do not.
> Again, I'm not a lawyer, so please do not use my layman's
> opinions as legal advice.
I am aware of several reasons your writings are not legal advice. As
another non-lawyer, though, I wanted to give you a chance to defend
your claims before I decide they are entirely meritless.
Michael
next prev parent reply other threads:[~2004-06-17 20:22 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
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 [this message]
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=87isdqx7cd.fsf@sanosuke.troilus.org \
--to=mdpoole@troilus.org \
--cc=adam@yggdrasil.com \
--cc=greg@kroah.com \
--cc=hch@lst.de \
--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