ergethaxsd

4 ms·

1. 1.▲
   by ergethaxsd 11y ago

   > "When the firmware is freely redistributable, it's also included in the kernel source tree. Nothing more, nothing less. It's up to you to decide what to do with it - you can easily look up all the needed info and remove
2. 2.▲
   by ergethaxsd 11y ago

   > "And even if it doesn't, because the most important parts of that non-free firmware are already sealed in memory on the card, it's no different from, let's take the easier example, any HDD out there." On the co
3. 3.▲
   by ergethaxsd 11y ago

   I don't think it's counterproductive at all and we actually agree in a sense. In a sense, opaque blobs are the default license category. Moving past that, if we can acknowledge that unambiguously (positively-stated) non-proprietar
4. 4.▲
   by ergethaxsd 11y ago

   (I'm saddened that you can't imagine ever needing to load FPGA, NAND, or VRAM "firmware" to boot a GPU.) > "the only sensible approach to differentiate between free and non-free firmwares is to ask a question &#x
5. 5.▲
   by ergethaxsd 11y ago

   Choice, like mutation and sexual reproduction, accelerates evolution. More options means better options over less time.
6. 6.▲
   by ergethaxsd 11y ago

   While it is naive to imply closed blobs could ever fully or easily be replaced, it is also naive to blame the kernel user for having bought the hardware. For add-on cards, sure, but the line is not always that clear. Many are simply making