Making life (even) harder for proprietary modules
Making life (even) harder for proprietary modules
Posted Aug 30, 2023 17:50 UTC (Wed) by cstrahan (guest, #104863)In reply to: Making life (even) harder for proprietary modules by dvdeug
Parent article: Making life (even) harder for proprietary modules
Sure. But it does make things better in a couple important ways: If NVIDIA wants to shove critical functionality into firmware blobs, at least the experience of using NVIDIA GPUs will suck equally everywhere. In practice, that means that they'll either work harder (than they would writing Linux kernel module code) to get things right, or if they can't, then they can be punished in the market, and we can all opt to acquire competing cards.
And while you and I would prefer to have access to all of the code, this move is still better than before for another reason: while the GPU may be stuck with buggy firmware blobs, at least that's not running in kernel space, with the power to crash your system.
Maybe an analogy would help: If I order food delivered, the delivery driver may take a crazy, convoluted route through town, and he may curb his vehicle, or get in a wreck, etc, and I don't have any control over that. But do you know what the delivery driver *isn't* going to do? Any of the above to *my* vehicle. If I *could* control the delivery driver's actions, I would have them safely and optimally delivery my food, but because I can't, at least I'll be happier knowing that they can only total their own car, while my car is sitting safely in my garage.
Having the proprietary NVIDIA kernel module loaded is like handing your keys over to a delivery driver you have never met and trusting they won't financially ruin you.