Implementing DRM format modifiers in NVK (www.collabora.com)
from joojmachine@lemmy.ml to linux@lemmy.ml on 16 May 2024 16:26
https://lemmy.ml/post/15710128

The tl;dr for those like me, who don’t understand the technical parts:

This week we merged support for the VK_EXT_image_drm_format_modifier extension in NVK, the new open-source Vulkan driver for NVIDIA hardware. We’ve also back-ported the code to the Mesa 24.1 staging branch so it will be part of the upcoming Mesa 24.1 release.

DRM format modifier support is one of the most important features we’ve landed in NVK in a while. Though it’s not a very interesting feature to most Vulkan applications or game developers, it’s very important to the Linux display pipeline. Importantly to users, this is the last piece required to support GameScope. It’s also an important piece in making Zink+NVK a robust OpenGL solution.

#linux

threaded - newest

GolfNovemberUniform@lemmy.ml on 16 May 2024 18:54 collapse

DRM = bad. Consider forking.

fossphi@lemm.ee on 16 May 2024 19:25 next collapse

Umm, this isn’t about that DRM

GolfNovemberUniform@lemmy.ml on 16 May 2024 19:32 collapse

I suspected so and tbh idk why I even made the comment. I guess I’m more unstable than usual at the moment

Penta@lemmy.world on 16 May 2024 21:32 next collapse

DRM = Direct Rendering Manager, not Digital Rights Management here

acockworkorange@mander.xyz on 17 May 2024 13:14 collapse

And to preempt the question: direct rendering manager predates digital rights management.

secret300@lemmy.sdf.org on 17 May 2024 22:08 next collapse

Haha, I always think of digital rights management at first too but it’s actually talking about direct rending something

possiblylinux127@lemmy.zip on 19 May 2024 02:57 collapse

DRM stands for direct rendering manager. You can’t even use your computer without the rendering manager to interface your desktop and applications with your GPU.