AMD submits initial RDNA5/GFX13 enablement to Mesa RADV and RadeonSI drivers

AMD has submitted the first Mesa merge request to enable GFX13 hardware support in its open-source RADV Vulkan and RadeonSI Gallium3D/OpenGL drivers, following earlier kernel-side AMDGPU patches submitted this week. This initial code is described as very primitive and consists primarily of chip ID definitions and descriptor changes for both drivers. The merge request represents only the foundation of RDNA5 graphics enablement, with substantial follow-up work still required including ACO compiler back-end modifications and full register support. AMD GFX13 is widely understood to correspond to the RDNA5 generation of Radeon GPUs expected to begin shipping in late 2027.

The timing indicates AMD is beginning its open-source driver bring-up unusually early relative to hardware availability, continuing the company's established practice of upstream-first development for Linux graphics. The kernel-side AMDGPU patches and now this Mesa merge request suggest a coordinated multi-layer driver effort. Additional merge requests will be needed over the coming weeks and months before the drivers achieve functional rendering capability on GFX13 hardware.

What the initial GFX13 Mesa enablement includes

• Chip identification: The merge request adds initial GFX13 chip ID definitions to both RADV and RadeonSI, allowing the drivers to recognize the new hardware family at initialization time.
• Descriptor changes: Both the Vulkan and OpenGL drivers receive hardware descriptor modifications needed for basic GFX13 compatibility, though these are not yet sufficient for actual rendering.
• ACO compiler pending: The ACO (AMD Compiler Optimizer) back-end used by RADV for shader compilation does not yet have GFX13 register definitions or instruction support; this is explicitly noted as follow-up work.
• RadeonSI Gallium3D scope: The OpenGL driver enablement parallels the RADV Vulkan work, ensuring both major Mesa driver paths receive simultaneous foundational support rather than prioritizing one API.
• Kernel dependency: This user-space work follows AMDGPU kernel driver patches submitted earlier in the same week, indicating coordinated bring-up across the full Linux graphics stack.

Why it matters

Early open-source driver enablement for unreleased AMD hardware preserves the company's competitive advantage in Linux graphics support, giving distributions and enthusiasts confidence that RDNA5 GPUs will have functional drivers at or near hardware launch rather than months later. For the Mesa development community, this provides visibility into upcoming architectural changes and time to prepare compiler and tooling infrastructure before hardware availability. The coordinated kernel and user-space posting also demonstrates AMD's continued commitment to upstream-first development, reinforcing the open-source Radeon driver stack as a reference implementation for new GPU generations.