From: Ian Stirling <ian.stirling@mauve.plus.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Patrick McFarland <diablod3@gmail.com>,
Anonymous User <anonymouslinuxuser@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: GPL Violation?
Date: Fri, 18 Aug 2006 00:45:13 +0100 [thread overview]
Message-ID: <44E4FF89.3080500@mauve.plus.com> (raw)
In-Reply-To: <1155807431.22871.157.camel@pmac.infradead.org>
David Woodhouse wrote:
<snip>
> So when you distribute a product which combines the kernel and some
> driver module, and which isn't 'mere aggregation on a storage medium'
> but is actually a coherent whole which works together and wouldn't
> function correctly if either the kernel or the module were missing, then
> your module _must_ be released under the terms of the GPL too.
'function correctly' ?
As what?
I've bought a number of devices that I know will not have all the
advertised features available to me, because I install a different
version of linux on them.
It functions correctly, as delivered.
With the appropriate disclaimers on the box, it cannot function
incorrectly, as you will know that the thumb-print reader won't
work if you upgrade the kernel, and if you intend to do so,
you don't buy.
I've got a number of wireless routers that I don't have working
drivers for the wifi cards, happily wired into my network doing
things that they were not intended for, but they are functioning
'correctly' as I see it.
next prev parent reply other threads:[~2006-08-17 23:45 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 5:48 GPL Violation? Anonymous User
2006-08-17 6:14 ` Arjan van de Ven
2006-08-17 9:38 ` Ben B
2006-08-17 12:02 ` linux-os (Dick Johnson)
2006-08-17 16:11 ` Stefan Richter
2006-08-17 19:21 ` James Courtier-Dutton
2006-08-17 23:26 ` Ian Stirling
[not found] ` <20060817193540.dc819396.seanlkml@sympatico.ca>
2006-08-17 23:35 ` Sean
2006-08-18 0:32 ` Alan Cox
2006-08-18 7:23 ` Xavier Bestel
2006-08-18 12:23 ` Ian Stirling
2006-08-18 9:04 ` Helge Hafting
2006-08-17 6:42 ` Patrick McFarland
2006-08-17 6:54 ` Arjan van de Ven
2006-08-17 7:32 ` Patrick McFarland
2006-08-17 8:02 ` Adrian Bunk
2006-08-17 9:03 ` Patrick McFarland
2006-08-18 17:56 ` Adrian Bunk
2006-08-17 12:39 ` Grzegorz Kulewski
2006-08-17 13:41 ` Alan Cox
2006-08-17 13:31 ` Grzegorz Kulewski
2006-08-17 15:52 ` Theodore Tso
2006-08-18 2:03 ` Chase Venters
2006-08-17 8:32 ` Stefan Richter
2006-08-17 9:36 ` Patrick McFarland
2006-08-17 11:25 ` Alan Cox
2006-08-17 11:48 ` Neil Brown
2006-08-17 9:37 ` David Woodhouse
2006-08-17 23:45 ` Ian Stirling [this message]
2006-08-18 8:28 ` David Woodhouse
2006-08-18 12:52 ` Ian Stirling
2006-08-18 8:53 ` Bernd Petrovitsch
2006-08-18 9:04 ` David Woodhouse
2006-08-18 9:15 ` Bernd Petrovitsch
2006-08-20 22:05 ` Andrea Arcangeli
2006-08-20 22:20 ` Arjan van de Ven
2006-08-18 9:51 ` David Schwartz
2006-08-18 16:52 ` Alan Cox
2006-08-18 22:42 ` David Schwartz
2006-08-19 10:48 ` David Greaves
2006-08-19 16:29 ` Patrick McFarland
2006-08-19 17:28 ` David Greaves
2006-08-19 11:30 ` Helge Hafting
2006-08-19 15:44 ` Michael Buesch
2006-08-19 23:01 ` David Schwartz
2006-08-20 3:20 ` Chase Venters
2006-08-21 7:58 ` Helge Hafting
2006-08-21 11:27 ` Stefan Richter
2006-08-21 13:06 ` Alan Cox
2006-08-21 14:59 ` Horst H. von Brand
2006-08-17 9:30 ` Alan Cox
2006-08-17 9:29 ` Patrick McFarland
2006-08-17 14:52 ` Helge Hafting
2006-08-17 14:58 ` Anonymous User
2006-08-17 15:52 ` Stefan Richter
2006-08-17 16:19 ` Michiel de Boer
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=44E4FF89.3080500@mauve.plus.com \
--to=ian.stirling@mauve.plus.com \
--cc=anonymouslinuxuser@gmail.com \
--cc=diablod3@gmail.com \
--cc=dwmw2@infradead.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