Meanwhile Nvidia continues doing whatever they want instead of cooperating with everyone like Intel and AMD.
„nvidia, fuck you“ - linus torvalds
You forgot the 🖕 at the end (it’s very important)
Not trying to shill, but they’ve stepped up with open sourcing their kernel modules and implementing wayland explicit sync (though not implementing implicit sync continues to screw users until the stack is complete). Their driver situation is far better than it was in the past.
Most games I currently played are affected by their decision to not implement implicit sync. I’m back to X11 until there is a solution.
+1, also waiting for the solution. I’m still on Wayland, but I have to use driver 535 to avoid major corruption issues with xwayland. There’s still issues with that driver, but it’s at least usable for me.
I’m getting a headache trying to understand this title.
This is the best summary I could come up with:
As part of the AMD color management and HDR efforts worked on by AMD Linux engineers along with Valve and other stakeholders like Igalia developers, Intel engineers have posted their plane color pipeline implementation that follows the cross-vendor API proposal.
AMD and other parties have been working on this color pipeline API for months and also implementing it in the VKMS DRM driver for reference purposes.
The DRM core changes for the color pipeline support still need to be merged while now havinfg this Intel implementation available should help in seeing consensus as well as getting the desktop/compositor developers to make use of the user-space API.
As a refresher on the Linux Color Pipeline API: "We would like to support pre-, and post-blending complex color transformations in display controller hardware in order to allow for HW-supported HDR use-cases, as well as to provide support to color-managed applications, such as video or image editors.
We would like to make use of this HW functionality to support complex color transformations with no, or minimal CPU or shader load."
Currently the Intel implementation is 27 patches and can be found out for review on the dri-devel mailing list.
The original article contains 339 words, the summary contains 195 words. Saved 42%. I’m a bot and I’m open source!
