this post was submitted on 11 May 2024
230 points (97.5% liked)

Linux Gaming

15250 readers
38 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] woelkchen@lemmy.world 111 points 6 months ago (9 children)

The headline is misleading. It's only about the kernel module. The driver itself will stay proprietary.

[–] Jajcus@kbin.social 5 points 6 months ago* (last edited 6 months ago) (4 children)

But this is the part where being open source is most important. For security, maintainability and convenience reasons

One could even argue if the usespace part, the OpenGl or Vulkan implementation, is still 'a driver'. (I think it is, at least partially)

[–] h3ndrik@feddit.de 3 points 6 months ago (2 children)

I'm not sure. Didn't they just move the code that was previously executed in the proprietary kernel module to the new also proprietary userspace driver that's just connected to the hardware by this new and open source wrapper module? And the other half into firmware? It's still arbitrary and closed code that gets forwarded to the hardware. And running there it has access to all the memory, screen content etc... I'm not sure if this is a win concerning security. I think it's pretty much unchanged.

But there are several big advantages. Now the kernel probably won't get tainted any longer and we can have signed kernels and activate secure boot easily. And that's maybe a big plus for security. And I hope we'll get the convenience, too. In the past I had the NVidia driver crap out on me while debugging stuff with recent kernel versions or release candidates. And NVidia was lagging behind, leaving me with a console instead of the desktop environment...

[–] Jajcus@kbin.social 3 points 6 months ago (1 children)

Didn’t they just move the code that was previously executed in the proprietary kernel module to the new also proprietary userspace driver

Probably. And that is exactly what was expected from them since the beginning of their Linux drivers. Kernel is not a place for such big and proprietary piece of code. So this is the important change.

Yes, the driver is still proprietary, but it does not break the kernel any more the way it did.

[–] h3ndrik@feddit.de 2 points 6 months ago

it does not break the kernel any more the way it did.

Hehe, yeah that'd be hard to achieve.

load more comments (1 replies)
load more comments (5 replies)