News: 0001528644

  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.0 Released With Vulkan 1.4 Driver Support, AMD RDNA4 Ready

([Mesa] 21 Minutes Ago Mesa 25.0)


[1]Mesa 25.0 was officially released today as the newest quarterly feature release for this set of open-source OpenGL, OpenCL, Vulkan, and video acceleration drivers used on Linux systems by multiple hardware vendors.

Mesa 25.0 brings usable support for AMD Radeon RX 90x0 "RDNA4" graphics with the RadeonSI Gallium3D (OpenGL) and RADV (Vulkan) drivers. The RadeonSI support should be in great shape given it's worked on directly by AMD while the RADV RDNA4 support is tackled by Valve developers and the initial RDNA4 support is deemed good enough.

Also exciting on the RADV side with Mesa 25.0 is adding Vulkan 1.4 support for that API update introduced in December. The other prominent Mesa Vulkan drivers have also landed Vulkan 1.4 support.

Another win for AMD with Mesa 25.0 is enabling the ACO compiler back-end by default for pre-RDNA GPUs with the RadeonSI Gallium3D driver. ACO as an alternative to the AMDGPU LLVM shader compiler has seen much work the past quarter. There is also initial AMD user-queue Mesa support for submitting work directly to the GPU(s) to bypass more of the kernel driver overhead. Plus other never-ending work on graphics driver performance optimizations.

Mesa 25.0 is also bringing various Zink OpenGL-on-Vulkan enhancements, many new Vulkan extensions supported by the Arm Mali "PanVK" driver, better Qualcomm Adreno Vulkan support with Turnip, and various Intel Xe2 optimizations for Lunar Lake and Battlemage. The Intel ANV Vulkan driver also now supports AV1 video decoding and other new features. The NVK Vulkan driver for NVIDIA GPUs has also seen continued refinements and new feature support.

Mesa 25.0 is a very jam packed release especially for the AMD Radeon and Intel graphics drivers as usual plus respectable work to the various other OpenGL and Vulkan drivers within this large codebase.

The Mesa 25.0 release announcement can be read on the [2]Mesa mailing list .



[1] https://www.phoronix.com/search/Mesa+25.0

[2] https://lists.freedesktop.org/archives/mesa-dev/2025-February/226464.html



phoronix

Dear Emily:
I'm still confused as to what groups articles should be posted
to. How about an example?
-- Still Confused

Dear Still:
Ok. Let's say you want to report that Gretzky has been traded from
the Oilers to the Kings. Now right away you might think rec.sport.hockey
would be enough. WRONG. Many more people might be interested. This is a
big trade! Since it's a NEWS article, it belongs in the news.* hierarchy
as well. If you are a news admin, or there is one on your machine, try
news.admin. If not, use news.misc.
The Oilers are probably interested in geology, so try sci.physics.
He is a big star, so post to sci.astro, and sci.space because they are also
interested in stars. Next, his name is Polish sounding. So post to
soc.culture.polish. But that group doesn't exist, so cross-post to
news.groups suggesting it should be created. With this many groups of
interest, your article will be quite bizarre, so post to talk.bizarre as
well. (And post to comp.std.mumps, since they hardly get any articles
there, and a "comp" group will propagate your article further.)
You may also find it is more fun to post the article once in each
group. If you list all the newsgroups in the same article, some newsreaders
will only show the article to the reader once! Don't tolerate this.
-- Emily Postnews Answers Your Questions on Netiquette