From: "Chris Friesen" <cfriesen@nortel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Pavel Roskin <proski@gnu.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jon Masters <jcm@jonmasters.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH 2.6.25] module: allow ndiswrapper to use GPL-only symbols
Date: Fri, 29 Feb 2008 10:54:29 -0600 [thread overview]
Message-ID: <47C838C5.8030707@nortel.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0802290807110.17889@woody.linux-foundation.org>
Linus Torvalds wrote:
>
> On Fri, 29 Feb 2008, Pavel Roskin wrote:
>
>>>I'm not seeing why ndiswrapper should be treated separately.
>>
>>It is already treated separately, and has been for a long time.
>
>
> No, I mean "separately from the thing it loads".
>
> It loads non-GPL code, it is non-GPL.
But the GPL only applies to derivative works. Given that ndiswrapper
loads binaries designed for another OS, doesn't that mean that it is
unlikely that the binaries would be impacted by the GPL?
So the portion that is a derivative work (ndiswrapper itself) is GPL,
and it loads something that is clearly not a derivative work. From a
licensing standpoint how is this different than an open-source driver
loading a proprietary firmware?
Once ndiswrapper loads the binary blob the kernel should be considered
tainted from a debuggability standpoint, but I have some sympathy for an
argument suggesting that ndiswrapper should be able to use GPLONLY symbols.
Chris
next prev parent reply other threads:[~2008-02-29 16:56 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 22:11 [PATCH 2.6.25] module: allow ndiswrapper to use GPL-only symbols Pavel Roskin
2008-02-28 23:25 ` Linus Torvalds
2008-02-29 6:20 ` Pavel Roskin
2008-02-29 16:08 ` Linus Torvalds
2008-02-29 16:54 ` Chris Friesen [this message]
2008-02-29 17:06 ` Linus Torvalds
2008-02-29 17:59 ` Chris Friesen
2008-03-06 14:56 ` David Woodhouse
2008-02-29 16:59 ` Zan Lynx
2008-02-29 17:07 ` Linus Torvalds
2008-02-29 17:20 ` Pavel Roskin
2008-02-29 17:33 ` Linus Torvalds
2008-02-29 19:39 ` Pavel Roskin
2008-02-29 19:53 ` Linus Torvalds
2008-02-29 20:08 ` Pavel Roskin
2008-02-29 20:28 ` Linus Torvalds
2008-02-29 21:13 ` Pavel Roskin
2008-02-29 20:17 ` John W. Linville
2008-02-29 20:40 ` David Newall
2008-02-29 20:59 ` Pavel Roskin
2008-02-29 21:08 ` David Newall
2008-02-29 22:17 ` Pavel Roskin
2008-03-01 8:15 ` David Newall
2008-02-29 20:44 ` Pavel Roskin
2008-02-29 21:15 ` Ingo Molnar
2008-02-29 22:31 ` Pavel Roskin
2008-03-03 10:57 ` Ingo Molnar
2008-03-04 5:37 ` Pavel Roskin
2008-03-04 12:57 ` Ingo Molnar
2008-03-04 17:19 ` Linus Torvalds
2008-03-04 17:38 ` Greg KH
2008-03-04 17:45 ` Pavel Roskin
2008-03-04 21:20 ` Ingo Molnar
2008-03-04 23:23 ` Pavel Roskin
2008-03-04 20:51 ` Ingo Molnar
2008-03-04 23:25 ` Jiri Kosina
2008-03-05 13:21 ` Ingo Molnar
2008-02-29 17:18 ` Jon Masters
2008-02-29 21:55 ` Adrian Bunk
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=47C838C5.8030707@nortel.com \
--to=cfriesen@nortel.com \
--cc=jcm@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.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