From: Zan Lynx <zlynx@acm.org>
To: Jon Masters <jonathan@jonmasters.org>
Cc: Pavel Roskin <proski@gnu.org>,
linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>,
Giridhar Pemmasani <pgiri@yahoo.com>
Subject: Re: ndiswrapper and GPL-only symbols redux
Date: Tue, 29 Jan 2008 22:38:11 -0700 [thread overview]
Message-ID: <47A00D43.60602@acm.org> (raw)
In-Reply-To: <20080130050424.GA22444@dallas.jonmasters.org>
Jon Masters wrote:
> I wouldn't quite say that. I wasn't going to comment, but...personally,
> I actually disagree with the assertions that ndiswrapper isn't causing
> proprietary code to link against GPL functions in the kernel (how is
> an NDIS implementation any different than a shim layer provided to
> load a graphics driver?), but I wasn't trying to make that point.
Well, as long as *any* part of the kernel ever links to proprietary
code, then GPL functions link to it in exactly the same way ndiswrapper
enables. It's only a matter of how many steps of separation.
A perfectly GPL USB network driver linked to GPL-only functions feeds
data into the kernel where it swirls about and emerges from a
proprietary network filesystem driver, for example.
next prev parent reply other threads:[~2008-01-30 5:38 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 21:22 ndiswrapper and GPL-only symbols redux Pavel Roskin
2008-01-29 22:27 ` Valdis.Kletnieks
2008-01-29 22:35 ` Giridhar Pemmasani
2008-01-29 23:21 ` Pavel Roskin
2008-01-30 0:25 ` Jon Masters
2008-01-29 22:45 ` Alan Cox
2008-01-29 23:56 ` Pavel Roskin
2008-01-30 3:24 ` Andi Kleen
2008-01-30 5:07 ` Jon Masters
2008-01-30 5:26 ` Pavel Roskin
2008-01-30 6:03 ` Andi Kleen
2008-01-30 6:12 ` Pavel Roskin
2008-01-29 22:57 ` Adrian Bunk
2008-01-29 23:04 ` Alan Cox
2008-01-29 23:06 ` Jan Engelhardt
2008-01-29 23:25 ` Måns Rullgård
2008-01-30 0:35 ` Adrian Bunk
2008-01-30 0:46 ` Måns Rullgård
2008-01-30 1:44 ` Daniel Hazelton
2008-01-30 7:38 ` Geert Uytterhoeven
2008-01-30 8:45 ` Måns Rullgård
2008-01-30 21:00 ` David Schwartz
2008-01-29 23:44 ` Pavel Roskin
2008-01-30 0:25 ` Adrian Bunk
2008-01-30 2:02 ` Pavel Roskin
2008-01-30 11:24 ` Rusty Russell
2008-01-30 17:54 ` Adrian Bunk
2008-01-30 18:15 ` Lennart Sorensen
2008-01-30 18:45 ` Adrian Bunk
2008-01-30 19:43 ` Lennart Sorensen
2008-01-30 20:26 ` Valdis.Kletnieks
2008-01-30 21:09 ` Adrian Bunk
[not found] ` <E1JKJvh-0006P8-Pi@fencepost.gnu.org>
2008-02-01 5:08 ` Pavel Roskin
2008-02-06 10:50 ` Adrian Bunk
2008-02-06 11:11 ` Xavier Bestel
2008-02-06 11:38 ` David Schwartz
2008-02-06 15:10 ` Theodore Tso
2008-01-30 0:48 ` Giridhar Pemmasani
2008-01-30 17:54 ` Adrian Bunk
2008-01-30 18:26 ` Chris Friesen
2008-01-30 18:54 ` Adrian Bunk
2008-01-30 19:36 ` Lee Revell
2008-01-30 20:28 ` Adrian Bunk
2008-01-31 1:00 ` Michael Gerdau
2008-02-05 13:00 ` Adrian Bunk
2008-02-04 12:42 ` Alan Cox
2008-02-04 13:56 ` Adrian Bunk
2008-01-31 3:25 ` David Newall
2008-01-31 15:20 ` Chris Friesen
2008-01-30 0:20 ` Jon Masters
2008-01-30 0:35 ` Jan Engelhardt
2008-01-30 0:48 ` Jon Masters
2008-01-30 1:33 ` Pavel Roskin
2008-01-30 1:48 ` Pavel Roskin
2008-01-30 2:08 ` Jan Engelhardt
2008-01-30 5:04 ` Jon Masters
2008-01-30 5:38 ` Zan Lynx [this message]
2008-01-30 7:40 ` Geert Uytterhoeven
2008-01-30 8:54 ` Måns Rullgård
2008-01-30 20:50 ` David Schwartz
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=47A00D43.60602@acm.org \
--to=zlynx@acm.org \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgiri@yahoo.com \
--cc=proski@gnu.org \
--cc=rusty@rustcorp.com.au \
/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