AMD’s RDNA 4m Firmware Upload Puts Medusa Point APUs Close to Linux Readiness

Together, these files represent more than a new device ID in a driver. They cover multiple IP blocks that an integrated GPU platform needs to initialize and operate as a complete graphics system. The upload therefore makes the GFX 11.7 software path look substantially more mature than it did when support existed only in development versions of the kernel, compiler, and graphics stack.

Why the firmware timing matters

Firmware is a necessary part of the Linux hardware-support chain, but it is normally only one layer. The kernel must recognize the hardware, LLVM must be able to compile shaders for it, and Mesa must expose the relevant Vulkan and OpenGL paths.

AMD has already been staging GFX 11.7 changes in the AMDGPU kernel driver and LLVM’s AMDGPU compiler backend. Mesa 26.3 then added GFX1171 support to both RADV, the Vulkan driver, and RadeonSI, the OpenGL driver. The Mesa change largely gives GFX1171 the identifiers and existing code paths needed to follow the earlier GFX1170 implementation.

That sequencing is significant for distributions. If firmware reaches linux-firmware ahead of hardware availability, distributions have time to include it in system updates. Users are consequently more likely to receive a usable graphics stack without relying on a vendor-specific installer or a manual firmware download.

GFX1172 is still missing

The upload includes GFX1170 and GFX1171 firmware, but not GFX1172. AMD’s compiler and driver work has identified GFX1170, GFX1171, and GFX1172 as targets within the RDNA 4m family, and the available code follows the same ISA capability paths for these targets.

The absence of GFX1172 could reflect a later product, a variant that is not ready for public firmware staging, or a separate release schedule. It is not enough to prove a specific product segmentation strategy. It also means that the current firmware upload should not be described as complete support for every known GFX117x target.

What “RDNA 4m” tells us—and what it does not

GFX 11.7 sits numerically between RDNA 3.5’s GFX 11.5 and discrete RDNA 4’s GFX 12.0. AMD’s open-source development work groups the GFX1170, GFX1171, and GFX1172 identifiers under the “RDNA 4m” label, but those identifiers are internal graphics targets rather than retail product names.

The available evidence supports treating RDNA 4m as an intermediate or derivative graphics branch intended for an APU or SoC-oriented platform. The “m” may indicate a mobile or integrated-graphics focus, particularly because reporting has connected the work with the unannounced Medusa Point family. However, AMD has not publicly defined the suffix or formally confirmed that every GFX117x target belongs to Medusa Point.

The code also does not reveal the specifications that buyers would normally want to know. There is no confirmed product name, compute-unit count, clock speed, memory configuration, performance target, or launch date attached to GFX1171 in the cited reporting.

The likely Linux software baseline

For users evaluating a future GFX 11.7 system, the safest expectation is a distribution with all four relevant pieces aligned:

1. A kernel containing the upstream GFX 11.7 AMDGPU work
2. Current linux-firmware packages containing the required blobs
3. LLVM support for the relevant GFX117x compiler target
4. Mesa 26.3 or newer for the clearest GFX1171 RADV and RadeonSI baseline

Linux 7.3 is the logical target for the complete upstream kernel-side enablement because AMD’s GFX 11.7 and DCN 4.2 changes were being staged for that kernel cycle. Mesa 26.2 may cover some earlier GFX1170 work, but the available evidence makes Mesa 26.3 the safer recommendation for a system using GFX1171.

This is a software-readiness assessment, not a guarantee that every distribution will ship identical support on the same day. Distribution kernels and Mesa packages can lag upstream development, and the missing GFX1172 firmware shows that enablement is still being staged in phases.

The UALink patches are a separate story

AMD also submitted a large Linux kernel patch series for UALink around the same time. UALink is an accelerator interconnect and networking standard aimed at connecting GPUs and other AI accelerators in data-center scale-up systems.

The timing reflects broad AMD upstream activity, but it should not be treated as evidence that Medusa Point APUs use UALink. The RDNA 4m firmware upload concerns an integrated graphics platform and its Linux graphics stack; the UALink work targets accelerator infrastructure.

Bottom line

AMD’s RDNA 4m firmware staging materially strengthens the case that GFX 11.7 hardware is approaching availability and that Linux support is being prepared unusually early. The combination of firmware, AMDGPU kernel work, LLVM support, and Mesa development points toward a launch with a much more complete open-source graphics foundation than a platform revealed only after release.

For Medusa Point, however, the correct conclusion is “closer to launch,” not “officially announced.” The upload does not confirm the processor family, exact SKUs, performance, or release date—and GFX1172 remains outside the published firmware set. The most defensible expectation is a forthcoming APU-class platform with strong Linux support, best experienced with current linux-firmware, Linux 7.3-era kernel support, and Mesa 26.3 or newer.