From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Giridhar Pemmasani <pgiri@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: incorrect taint of ndiswrapper
Date: Tue, 24 Oct 2006 15:07:10 +0100 [thread overview]
Message-ID: <1161698830.22348.30.camel@localhost.localdomain> (raw)
In-Reply-To: <20061024024347.57840.qmail@web32414.mail.mud.yahoo.com>
Ar Llu, 2006-10-23 am 19:43 -0700, ysgrifennodd Giridhar Pemmasani:
> I was not fully aware of this issue until now (I have read posts related to
> this issue now). Does this mean that any module that loads binary code can't
> be GPL, even those that load firmware files? How is
Firmware is usually more clearly separated (the problem ultimately is
that "derived work" is a legal not a technical distinction).
> non-GPL-due-to-transitivity going to be checked? Why does module loader mark
> only couple of modules as non-GPL, when there are other drivers that load
> some sort of binary code? It is understandable to mark a module as non-GPL if
> it is lying about its license, but as far as that is concerned, ndiswrapper
> (alone) is GPL.
Yes. I don't think the current situation is neccessarily correct, but if
it uses EXPORT_SYMBOL_GPL then the "now taint me" ought to fail and the
driver ought to refuse to load a non GPL windows driver.
Alan
next prev parent reply other threads:[~2006-10-24 14:03 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 5:41 incorrect taint of ndiswrapper 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 [this message]
2006-10-23 18:36 ` Zan Lynx
2006-10-24 11:59 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2006-10-25 20:11 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
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-27 4:32 ` Florin Malita
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=1161698830.22348.30.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pgiri@yahoo.com \
/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