From: Adrian Cox <adrian@humboldt.co.uk>
To: John Bradford <john@grabjohn.com>
Cc: Jamie Lokier <jamie@shareable.org>,
Stan Bubrouski <stan@ccs.neu.edu>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [OT] use of patented algorithms in the kernel ok or not?
Date: 22 Dec 2003 15:34:15 +0000 [thread overview]
Message-ID: <1072107256.28039.321.camel@newt> (raw)
In-Reply-To: <200312220950.hBM9o7Xr000488@81-2-122-30.bradfords.org.uk>
On Mon, 2003-12-22 at 09:50, John Bradford wrote:
> Quote from Jamie Lokier <jamie@shareable.org>:
>
> > That's why I said it's uncharted territory. We don't know how safe it
> > is to publish code that *doesn't do anything* but does embody a
> > patented technique *only if the recipient deliberately modifies the
> > code*.
>
> Look at the MTD code.
For examples of source code distribution in a patented area, look at
MPEG4 projects, particularly MPEG4IP.
http://mpeg4ip.sourceforge.net/ has source code under a variety of
licenses including GPL, and the front page has the following disclaimer:
"This code is not intended for end users, and does not contain
executables. Please read all the legal information to determine if it is
suitable for you."
The project was started by Cisco, who likely did some legal research
first. Cisco, however, have the resources to see off frivolous lawsuits,
while individual developers do not.
- Adrian Cox
http://www.humboldt.co.uk/
next prev parent reply other threads:[~2003-12-22 15:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-21 1:12 [OT] use of patented algorithms in the kernel ok or not? Albert Cahalan
2003-12-21 10:53 ` Jamie Lokier
2003-12-21 13:35 ` James Morris
2003-12-21 14:30 ` Jamie Lokier
2003-12-21 16:03 ` Xavier Bestel
2003-12-21 14:56 ` Arjan van de Ven
2003-12-21 19:33 ` Stan Bubrouski
2003-12-21 23:25 ` Helge Hafting
2003-12-21 19:29 ` Stan Bubrouski
2003-12-21 19:55 ` Matthias Schniedermeyer
2003-12-21 20:11 ` Stan Bubrouski
2003-12-21 21:52 ` Francois Romieu
2003-12-21 21:57 ` Jamie Lokier
2003-12-22 9:50 ` John Bradford
2003-12-22 15:34 ` Adrian Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-22 1:43 James Lamanna
2003-12-22 11:32 ` Matti Aarnio
2003-12-18 23:11 Lennert Buytenhek
2003-12-19 6:10 ` Linus Torvalds
2003-12-19 7:38 ` Paul Jackson
2003-12-19 8:47 ` Arjan van de Ven
2003-12-19 11:38 ` Jan-Benedict Glaw
2003-12-20 17:28 ` Stefan Traby
2003-12-21 10:33 ` Jamie Lokier
2003-12-21 16:57 ` Pavel Machek
2004-01-13 15:35 ` Chuck Campbell
2004-01-13 19:35 ` Pavel Machek
2004-01-13 21:04 ` Richard B. Johnson
2003-12-22 0:37 ` jw schultz
2003-12-21 23:39 ` Lennert Buytenhek
2003-12-21 1:25 ` jw schultz
2003-12-21 19:40 ` Lennert Buytenhek
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=1072107256.28039.321.camel@newt \
--to=adrian@humboldt.co.uk \
--cc=jamie@shareable.org \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stan@ccs.neu.edu \
/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