|
|
|
|
|
by em-bee
83 days ago
|
|
a kernel driver is an extension to the kernel. yet, even with a clearly defined API it is a derived work of the kernel. one can use the same topic for a work of poetry for a similar aesthetic effect and that doesn't infringe other poems because the new poem does not depend on the original. the kernel driver is useless without the kernel |
|
Maybe, in some alternative universe, that could be correct but it isn't anywhere on Earth.
You can write a BSD-licensed driver as a Linux module and distribute it separately all you want - copyright law is OK with that.
The moment you insert the module into the kernel the whole thing, kernel + driver becomes a derivative work and you're forbidden from using it by the GPL - the license, not copyright... Copyright only gives the creators of the kernel the privileged power to impose that contractual restriction.
Long time ago, some BSD guys were trying to convince me that the GPL was primarily a weapon against BSD and other less restrictive licenses but I didn't believe it back then... boy, was I wrong.
You showed me how the GPL can be used for threats against the free modification of software by arguing for the addition of new, absurd powers to copyright - the opposite of what the GPL proponents are promoting it for. It's indeed a license that must be avoided at all cost.