Linux GPL and binary module exception clause?
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 21 lines · Jason Kingsland
Quoted 7 lines · Linus Torvalds
And in fact, when it comes to modules, the GPL issue is exactly the same. The kernel _is_ GPL. No ifs, buts and maybe's about it. As a result, anything that is a derived work has to be GPL'd. It's that simple.
...
- anything that has knowledge of and plays with fundamental internal Linux behaviour is clearly a derived work. If you need to muck around with core code, you're derived, no question about it.If that is the case, why the introduction of
EXPORT_SYMBOL_GPLandMODULE_LICENSE()?Specifying explicit boundaries for the module interface has legitimised binary-only modules.
This was the signal to developers of proprietary code that binary-only modules are tolerable.
Quoted 5 lines
Note that I said tolerable, not acceptable. Ref also the 'tainted' flag ("man 8 insmod")
My personal view is that Linux should mandate GPL for all modules in 2.6 and beyond.
GPL is about distribution.
e.g. NVidia can distribute .o file (with whatever license they have
to) and nvidia.{c,h} files (even under GPL license).
Then install.sh may do on behalf of user "gcc nvidia.c blob.o -o
nvidia.ko". Resulting module are not going to be distributed - it is already at hand of end-user. So no violation of GPL whatsoever.
Licensing is least technical issue regarding modules. But sure I would like to have open source drivers - at least then I
have chance to clean them up ;-)))
my 2 eurocents.
Signature · 7 lines
Ihar 'Philips' Filipau / with best regards from Saarbruecken.
-- _ _ _
Because the kernel depends on it existing. "init" |_|*|_|
literally _is_ special from a kernel standpoint, |_|_|*|
because its' the "reaper of zombies" (and, may I add, |*|*|*|
that would be a great name for a rock band).
-- Linus TorvaldsQuoted 11 lines · Ihar 'Philips' Filipau
GPL is about distribution.
e.g. NVidia can distribute .o file (with whatever license they have
to) and nvidia.{c,h} files (even under GPL license).
Theninstall.shmay do on behalf of user "gccnvidia.cblob.o -o
nvidia.ko". Resulting module are not going to be distributed - it is already at hand of end-user. So no violation of GPL whatsoever.Licensing is least technical issue regarding modules. But sure I would like to have open source drivers - at least then I
have chance to clean them up ;-)))
offtopic anyway since nvidia already provide prebuild binaries for linux at http://www.nvidia.com/object/linux.html ...
Quoted 6 lines · Ihar 'Philips' Filipau
GPL is about distribution.
e.g. NVidia can distribute .o file (with whatever license they have
to) and nvidia.{c,h} files (even under GPL license).
Theninstall.shmay do on behalf of user "gccnvidia.cblob.o -o
nvidia.ko". Resulting module are not going to be distributed - it is already at hand of end-user. So no violation of GPL whatsoever.
Open source still win if they do this. Anybody interested may then read the restricted source and find out how the chip works. They may then write an open driver from scratch, using the knowledge.
Helge Hafting
Quoted 10 lines · Helge Hafting
Quoted 6 lines · Ihar 'Philips' Filipau
GPL is about distribution.
e.g. NVidia can distribute .o file (with whatever license they have
to) and nvidia.{c,h} files (even under GPL license).
Theninstall.shmay do on behalf of user "gccnvidia.cblob.o -o
nvidia.ko". Resulting module are not going to be distributed - it is already at hand of end-user. So no violation of GPL whatsoever.
Quoted 4 lines
Open source still win if they do this. Anybody interested may then read the restricted source and find out how the chip works. They may then write an open driver from scratch, using the knowledge.
What I think he means is that nvidia.c only contains glue code and blob.o contains the secret parts just like the current driver from nvidia.
// Stefan
Quoted 19 lines · Stefan Smietanowski
Quoted 11 lines · Helge Hafting
Quoted 6 lines · Ihar 'Philips' Filipau
GPL is about distribution.
e.g. NVidia can distribute .o file (with whatever license they have
to) and nvidia.{c,h} files (even under GPL license).
Theninstall.shmay do on behalf of user "gccnvidia.cblob.o -o
nvidia.ko". Resulting module are not going to be distributed - it is already at hand of end-user. So no violation of GPL whatsoever.Quoted 4 lines
Open source still win if they do this. Anybody interested may then read the restricted source and find out how the chip works. They may then write an open driver from scratch, using the knowledge.
Quoted 4 lines
What I think he means is that
nvidia.conly contains glue code and blob.o contains the secret parts just like the current driver from nvidia.
Exactly.
Source code licensing from second parties is really pain in the ass.
At my previous job I had situation that piece of code was several
times. I beleive we were fourth company who bought it and incorporated into applience. But ask anyone "what kind of rights do we have for this stuff?" - no-one really can answer, since we-are-not-lawyers so better to tell no-one how we use it. Probably we even had no rights to fix bugs... who knows?..
Signature · 7 lines
Ihar 'Philips' Filipau / with best regards from Saarbruecken.
-- _ _ _
Because the kernel depends on it existing. "init" |_|*|_|
literally _is_ special from a kernel standpoint, |_|_|*|
because its' the "reaper of zombies" (and, may I add, |*|*|*|
that would be a great name for a rock band).
-- Linus Torvalds