News: 0001562948

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Mesa 25.3 Merges Vulkan WSI Support For Using Atomic Mode-Setting

([Mesa] 6 Hours Ago Mesa Vulkan WSI + Atomic KMS)


A nearly five year old merge request was merged today to Mesa Git for Q4's Mesa 25.3 release. This merge transitions the Vulkan windowing system integration (WSI) from using the DRM "legacy" kernel mode-setting APIs over to the modern [1]atomic mode-setting interfaces.

Jonathan Marek opened the merge request back in August 2020 for moving the Vulkan WSI display code over to using the Linux Direct Rendering Manager atomic mode-setting APIs rather than the "legacy" mode-setting APIs. The Vulkan WSI code within Mesa is common to the different Vulkan hardware drivers.

Besides moving to these APIs that have been well supported by the modern upstream Linux DRM/KMS drivers for years, the other notable advantage of this transition is it being a prerequisite for landing the DRM modifiers support.

For more information on this transition to the atomic mode-setting interfaces for the Vulkan WSI code can be found via [2]this Mesa merge .



[1] https://www.phoronix.com/search/atomic+mode-setting

[2] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6173


Danny3

V1tol

LeaPhant

... C++ offers even more flexible control over the visibility of member
objects and member functions. Specifically, members may be placed in the
public, private, or protected parts of a class. Members declared in the
public parts are visible to all clients; members declared in the private
parts are fully encapsulated; and members declared in the protected parts
are visible only to the class itself and its subclasses. C++ also supports
the notion of *_______friends*: cooperative classes that are
permitted to see each other's private parts.
-- Grady Booch, "Object Oriented Design with Applications"