Merged today to Mesa 26.2-devel was a reorganization of the AMD RadeonSI Gallium3D driver code to better separate the graphics and multimedia acceleration code from the rest of the driver.

This code hitting Mesa Git today cleans up a lot of the code and makes it easier for handling use-cases like RadoenSI driver builds without graphics (OpenGL) acceleration support as well as for now allowing RadeonSI driver builds just for multimedia support for video acceleration.

Since a few months ago was support for building the RadeonSI driver to build without graphics support if not needing OpenGL support but still wanting to build RadeonSI Gallium3D for its other state trackers. AMD driver engineer Pierre-Eric Pelloux-Prayer merged code now to move graphics and compute speciifc code into its own "gfx" subfolder and all the multimedia code of RadeonSI being within an "mm" folder. In turn is now an option for building the RadeonSI driver with multimedia hardware support, such as for the Video Acceleration API (VA-API), but not other support if PIPE_CONTEXT_MEDIA_ONLY is set.

[1]

[2]This merge has all the details on the code reorganization. Presumably this clean-up for allowing multimedia-only RadeonSI driver builds is for uses like AMD Instinct where the focus is on the AMD ROCm compute stack but also having multimedia acceleration too. In fact, with today's [3]AMD Instinct MI350P announcement , AMD devoted a slide to talking up the multimedia capabilities with the Instinct MI350P. OpenGL isn't needed nor supported there but multimedia acceleration can be important for some applications. Similarly, in a future world where you may only need Vulkan API acceleration with the RADV driver for graphics but still desiring VA-API video acceleration from RadeonSI.



[1] https://www.phoronix.com/image-viewer.php?id=2026&image=instinct_mi350p_multimedia_lrg

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

[3] https://www.phoronix.com/review/amd-instinct-mi350p