From: Pavel Roskin <proski@gnu.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: incorrect taint of ndiswrapper
Date: Thu, 26 Oct 2006 15:19:00 -0400 [thread overview]
Message-ID: <1161890340.9087.28.camel@dv> (raw)
In-Reply-To: <1161859199.12781.7.camel@localhost.localdomain>
On Thu, 2006-10-26 at 11:39 +0100, Alan Cox wrote:
> Really ndiswrapper shouldn't be using _GPLONLY symbols, that would
> actually make it useful to the binary driver afflicted again and more
> likely to be legal.
usb_register_driver is using EXPORT_SYMBOL_GPL_FUTURE, which means all
USB drivers will have to be GPL soon. This would disable the USB
support in ndiswrapper.
There is no other way to register USB drivers. Apparently, the USB
developers feel that every Linux USB driver should be considered a
derived work of Linux, and therefore should be under GPL.
This means that ndiswrapper would be considered as a derived work of
Linux. Since ndiswrapper is under GPL, it would suffer unfairly if the
meaning of EXPORT_SYMBOL_GPL is extended to restrict GPLed modules
capable of loading proprietary code into the kernel.
The second problem is sysfs. Again, using sysfs is only allowed to
GPLed modules for the same reason. Although ndiswrapper is not using
sysfs now, it would be unfair to restrict it from doing that in the
future.
It's not like the proprietary modules would be using Linux USB or sysfs
API - they are unaware of Linux. Only the free code can use it.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-10-26 19:19 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 20:11 incorrect taint of ndiswrapper Pavel Roskin
2006-10-25 20:30 ` Alan Cox
2006-10-25 20:40 ` Kyle Moffett
2006-10-25 21:04 ` Alan Cox
2006-10-25 21:06 ` Pavel Roskin
2006-10-25 21:33 ` David Weinehall
2006-10-25 22:02 ` Pavel Roskin
2006-10-25 22:54 ` Alan Cox
2006-10-25 22:58 ` Alan Cox
2006-10-26 3:23 ` David Weinehall
2006-10-26 13:13 ` Thierry Vignaud
2006-10-26 13:21 ` Gianluca Alberici
2006-10-26 3:59 ` Andrew Morton
2006-10-26 9:03 ` Gianluca Alberici
2006-10-26 10:39 ` Alan Cox
2006-10-26 12:21 ` Giacomo A. Catenazzi
2006-10-26 12:59 ` Gianluca Alberici
2006-10-26 14:41 ` Al Viro
2006-10-26 14:55 ` Alan Cox
2006-10-26 16:00 ` Stephen Hemminger
2006-10-26 16:26 ` Gianluca Alberici
2006-10-27 14:24 ` Arjan van de Ven
2006-10-27 15:14 ` Stephen Hemminger
2006-10-26 19:19 ` Pavel Roskin [this message]
2006-10-26 21:46 ` Adrian Bunk
2006-10-26 22:29 ` Pavel Roskin
2006-10-26 23:00 ` Adrian Bunk
2006-10-26 23:36 ` Sven-Haegar Koch
2006-10-27 0:57 ` Adrian Bunk
2006-10-26 23:47 ` Pavel Roskin
2006-10-27 12:52 ` Roland Kuhn
2006-10-27 15:53 ` Pavel Roskin
2006-10-26 17:26 ` [PATCH ??] " Randy Dunlap
2006-10-27 14:23 ` Arjan van de Ven
2006-10-27 15:27 ` Randy Dunlap
2006-10-27 18:26 ` Andrew Morton
2006-10-27 22:56 ` Florin Malita
2006-10-27 22:56 ` Randy Dunlap
2006-10-27 23:05 ` Alan Cox
2006-10-27 23:02 ` Randy Dunlap
2006-10-27 23:12 ` Florin Malita
2006-10-27 23:23 ` Oleg Verych
2006-10-29 11:27 ` Gianluca Alberici
2006-10-27 21:32 ` Florin Malita
2006-10-27 4:32 ` Florin Malita
-- strict thread matches above, loose matches on Subject: below --
2006-10-23 5:41 Giridhar Pemmasani
2006-10-23 5:53 ` Gianluca Alberici
2006-10-23 6:25 ` Chase Venters
2006-10-23 6:41 ` Giridhar Pemmasani
2006-10-23 6:48 ` Gianluca Alberici
2006-10-23 7:12 ` Chase Venters
2006-10-23 11:07 ` Giridhar Pemmasani
2006-10-23 9:10 ` Gianluca Alberici
2006-10-23 9:39 ` Michal Schmidt
2006-10-23 8:24 ` Bernd Petrovitsch
2006-10-23 10:41 ` Alan Cox
2006-10-23 11:35 ` Giridhar Pemmasani
2006-10-23 13:00 ` Alan Cox
2006-10-24 2:43 ` Giridhar Pemmasani
2006-10-24 3:11 ` Randy Dunlap
2006-10-24 12:12 ` Pekka Enberg
2006-10-24 12:22 ` Alan Cox
2006-10-24 14:07 ` Alan Cox
2006-10-23 18:36 ` Zan Lynx
2006-10-24 11:59 ` Jan Engelhardt
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=1161890340.9087.28.camel@dv \
--to=proski@gnu.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).