Earlier quoted context omitted.
both zfs and nvidia do it, don't they? Or at least they haven't been in trouble over it :)
Korg ships a module with their Kronos workstation that re-exports some GPL symbols as non-GPL. They also ship the source for the kernel itself, but "conveniently" forgot to include a patch they added for DRM that makes their synthesizer module (yes the synth runs in kernel space) fail to work properly if missing. Some obfuscated change to the CD-ROM subsystem (yes really, they stuck some unrelated protection in there…
Linux's GPLv2 licence is routinely violated (2015)
201–202 of 202 posts
Wouldn't it just be better to reimplement whatever functionality they require themselves without recurring to GPL modules that break the license and expose them to legal risk?
Re: Linux's GPLv2 licence is routinely violated (2015)
#202Earlier quoted context omitted.
both zfs and nvidia do it, don't they? Or at least they haven't been in trouble over it :)
Korg ships a module with their Kronos workstation that re-exports some GPL symbols as non-GPL. They also ship the source for the kernel itself, but "conveniently" forgot to include a patch they added for DRM that makes their synthesizer module (yes the synth runs in kernel space) fail to work properly if missing. Some obfuscated change to the CD-ROM subsystem (yes really, they stuck some unrelated protection in there…
You might want to report that Korg violation to Conservancy:
https://sfconservancy.org/copyleft-compliance/help.html
Since you are a Linux kernel developer, you might want to join their Linux GPL compliance program: