News report
AMD Adds More Next-Gen GPU Hardware Blocks for Linux 7.4
AMD's latest Linux 7.4 graphics pull adds VPE 3.0, MMHUB 5.0 and other new GPU IP blocks, while their exact future products remain unconfirmed.
On this page
AMD's Linux driver is gaining another batch of future GPU blocks
AMD has sent another AMDGPU feature pull toward DRM-Next for the Linux 7.4 development cycle. Although much of the October 2 pull is now bug-fix work, it also adds support for several previously unsupported hardware IP versions: OSSSYS 8.0.1, LSDMA 8.0.1, NBIF 7.10, SMUIO 15.0.3, MP 15.0.3, VPE 3.0 and MMHUB 5.0.
The same pull continues work on hardware blocks that had already appeared in AMD's upstream driver development, including GFX12.1, DCN 6 and SMU 15. This is concrete open-source driver enablement for upcoming AMD graphics hardware, but AMD has not publicly mapped every block in this pull to a named Radeon product or architecture.
| IP block | Version | Role / boundary |
|---|---|---|
| VPE | 3.0 | Video Processing Engine; a major version step, but no product assignment is confirmed |
| MMHUB | 5.0 | GPU memory-hub support for upcoming hardware |
| NBIF | 7.10 | Northbridge/interface block support |
| OSSSYS | 8.0.1 | New system IP version added by the pull |
| LSDMA | 8.0.1 | New DMA-engine IP version added by the pull |
| SMUIO | 15.0.3 | System-management I/O block support |
| MP | 15.0.3 | New MP IP version support |
VPE 3.0 is the clearest generational signal in this batch
VPE 3.0 stands out because it is a full major-version increment for AMD's Video Processing Engine. The kernel pull also adds MMHUB 5.0 and multiple 15.0.3 management/interface blocks, while continuing updates for GFX12.1 and DCN 6.
Those version numbers are useful evidence that AMD is preparing its open Linux graphics stack for hardware beyond today's shipping configurations. They are not enough to label the entire patch set as RDNA 5. AMD's block-by-block IP discovery model allows different products to combine hardware blocks independently, so assigning every new version to one future consumer GPU would go beyond the public evidence.
The pull also contains fixes that matter to current Radeon users
Alongside future-hardware enablement, AMD's pull includes an HDMI RGB limited-range fix, DisplayPort MST fixes, runtime power-management improvements, GPUVM work, reset updates and additional HDMI changes. AMDKFD receives SVM and reset fixes, while the legacy Radeon driver gets a connector-table addition for the Sun XVR-300 and a SPARC64-related fix.
That mix is normal for a late development-cycle graphics pull: new IP enablement can land beside fixes for existing hardware. It does not mean every listed fix depends on the new GPU blocks.
Linux 7.4 is still a development target
These changes are staged in the DRM development path for the upcoming Linux 7.4 cycle rather than being features users can assume are present in today's stable distribution kernels. The pull was sent as DRM feature work approached its cutoff, so the practical significance is readiness for future hardware rather than an immediate upgrade benefit.
For PC users, the useful takeaway is that AMD continues to upstream support ahead of unreleased graphics hardware. The exact consumer relevance will become clear only when AMD identifies products that use these blocks and the Linux 7.4 cycle completes.
Sources
Primary and technical sources
These sources support the reporting and analysis above. Current stories are updated when later evidence materially changes the facts.
01 Linux kernel mailing list / AMD
drm-next-7.4-2026-10-02 AMDGPU pull request02 Phoronix
AMD Sends In More New GPU Hardware Enablement For Linux 7.4, Bug Fixes
Related
Continue from here
Useful next steps selected from the same technical reference and publication system.
Technical guide
How to Back Up Installed Drivers in Windows 11
Export third-party driver packages from the Windows 11 driver store with PnPUtil, preserve them before a reinstall, and understand what the backup does and does not contain.
Technical guide
How to Roll Back a Device Driver in Windows 11: Device Manager, Previous Packages, Recovery, and Verification
Safely roll back a problematic Windows 11 device driver, handle an unavailable rollback button, use supported previous packages, and verify the result.
Technical guide
How to Manage Devices with PnPUtil in Windows 11
Use Windows 11 PnPUtil to enumerate, restart, enable, rescan, and inspect devices with Microsoft's built-in administration tool.
Compatibility & upgrades
How to Check a Driver’s Digital Signature in Windows 11
Check whether a Windows 11 driver package or driver file is digitally signed, understand catalog versus embedded signatures, and interpret what a valid signature actually proves.