Results 1 to 3 of 3
Thread: Kernel blobs and GPL
Enjoy an ad free experience by logging in. Not a member yet? Register.
- Join Date
- Jun 2009
Kernel blobs and GPL
I am just asking this for curiosity's sake - no political implications or anything. Thanks.
The binary blobs don't ship with the kernel, but are usually part of 3rd party proprietary drivers such as the nVidia or ATI drivers. There is usually a GPL'd "shim" module that serves to separate the blob from the kernel meaning that the kernel itself is not directly linked to any proprietary software. This is obviously questionable in itself.
Other than that you may find firmware for devices that is loaded with the drivers, the firmware itself being the original proprietary one from the manufacturer. This is not part of the kernel but is loaded to the device, e.g. wifi card.
The high road, of course, is to simply not use devices that don't have open-sourced drivers, but that leaves a significant chunk of the world unable to use Linux in any practical manner. The "necessary evil" then is to include binary BLOBs and allow those people to use their devices the same way they would in another operating system.
That being said, I'm not a kernel developer, so if someone else has a divergent opinion I'm all ears.
Wasn't the kernel GPL'd in the 1990s? I also don't understand the license fully, so perhaps that is one source of my confusion. But from what I understand, once a certain software is released under the GPL, it is supposed to remain free forever. And it is implicitly required by the four freedoms that the source code should be made available in order for a certain software to be free.
GPL software can and does live side-by-side with non-GPL software all the time. The only legal requirement when distributing a product that contains both is that the source code for the GPL software be made available. It does not "infect" software released under different license terms.Registered Linux user #270181