Journal molarmass192's Journal: Linux: Binary-only kernel modules and the GPL
Binary-only drivers are acceptable but they cannot be part of a "distribution" which includes the kernel. The key word here is "distribution" since the GPL prohibits redistribution of GPL'd work without source code. As a distributor, you can get around that limitation by either making the binary-only drivers separate downloads or place them on separate physical media from the kernel.
Let me try to explain why this is acceptable as I understand it. Almost all bin-only drivers use GPL'd wrappers. A GPL'd wrapper is simply a kernel module that is open source and which interfaces with the kernel for a binary-only driver. If the binary only driver then communicates solely via the API presented by it's wrapper then there is no violation of the GPL. This is tricky to explain but the concept is that since the author of the GPL'd wrapper and the bin-only module are one and the same, there is no GPL conflict since the copyright owner is free to redistribute without regards to the terms of the GPL.
Let me try to explain why this is acceptable as I understand it. Almost all bin-only drivers use GPL'd wrappers. A GPL'd wrapper is simply a kernel module that is open source and which interfaces with the kernel for a binary-only driver. If the binary only driver then communicates solely via the API presented by it's wrapper then there is no violation of the GPL. This is tricky to explain but the concept is that since the author of the GPL'd wrapper and the bin-only module are one and the same, there is no GPL conflict since the copyright owner is free to redistribute without regards to the terms of the GPL.
