News report
AMD Starts Adding GDDR7 Support to Its Linux Graphics Driver
New AMDGPU patches add a GDDR7 VRAM identifier alongside IH 8.0 and NBIF 7.10 hardware blocks, but they do not identify a shipping Radeon GPU.
On this page
AMD has submitted an explicit GDDR7 addition to AMDGPU
AMD engineers submitted a small but unusually clear Linux graphics-driver patch on September 21 that adds “GDDR7” to the list of VRAM names recognized by AMDGPU. The patch changes amdgpu_object.c so the driver can identify GDDR7 alongside existing memory types such as LPDDR5, HBM3E and HBM4.
The change is real upstream driver preparation, but its scope is narrow. It gives AMDGPU a name for the memory technology; by itself it does not establish a complete GDDR7 memory controller implementation, a supported graphics card, a memory speed, a bus width or a launch date.
| Patch work | What AMD explicitly adds | What it does not establish |
|---|---|---|
| GDDR7 VRAM name | Adds GDDR7 to AMDGPU’s VRAM-name table | A specific GPU, capacity, speed or memory bus |
| IH 8.0 | Adds support for a new Interrupt Handler IP version and discovery entry | Which retail product contains that block |
| NBIF 7.10 | Adds support for a new New Bus InterFace IP version | A Radeon model or launch schedule |
IH 8.0 and NBIF 7.10 show broader new-hardware enablement
The GDDR7 identifier arrived alongside larger AMDGPU series for two new hardware-block revisions. AMD’s IH 8.0 series adds a new Interrupt Handler implementation plus the corresponding IP-discovery support. A separate series adds NBIF 7.10, a new revision of AMD’s New Bus InterFace, together with its register definitions and discovery plumbing.
That combination is useful evidence that AMD is preparing the open-source driver for future graphics hardware rather than making an isolated naming cleanup. It still does not tell us that all three additions belong to one retail GPU. AMD’s patch descriptions do not name RDNA 5, a Radeon product, a board configuration or a commercial release window.
Why early Linux enablement matters for future Radeon hardware
AMDGPU is developed in the open, so support for new IP revisions can become visible before the consumer hardware using them is announced. Staging that work early gives kernel development and review time to happen ahead of product availability, which can reduce the amount of basic hardware enablement that has to arrive after launch.
That should not be confused with finished day-one support. A usable graphics stack also depends on other kernel components, firmware, Mesa userspace drivers and product-specific enablement. These September 21 submissions are development evidence, not proof that an unnamed future card is already fully supported by a released Linux distribution.
GDDR7 itself does not predict the performance of a future Radeon GPU
Moving to GDDR7 can enable higher memory data rates than typical GDDR6 implementations, but graphics-card bandwidth also depends on the selected memory speed and bus width. Capacity, cache architecture and the GPU core itself are separate variables. A driver string therefore cannot be converted into an FPS estimate or a memory-bandwidth figure.
For the memory technology itself, Core Tech Tips has a separate source-backed GDDR7 versus GDDR6 reference covering PAM3 signaling, bandwidth math and compatibility. The important news here is not that GDDR7 exists, but that AMD’s upstream Linux enablement has now started naming it explicitly alongside new graphics IP revisions.
Evidence status
What the patches confirm and what remains unknown
Confirmed
- AMD submitted a patch adding GDDR7 to AMDGPU’s VRAM-name table on September 21, 2026.
- AMD also submitted IH 8.0 and NBIF 7.10 enablement series in the same patch window.
- The patch submissions are Linux-driver development work rather than a retail product announcement.
Unconfirmed
- The patches do not name RDNA 5 or identify a specific Radeon graphics card using GDDR7.
- They do not establish memory capacity, data rate, bus width, GPU performance, pricing or a launch date.
- They do not by themselves establish complete support in a released stable kernel, Mesa stack or Linux distribution.
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 AMD / amd-gfx mailing list
[PATCH] drm/amdgpu: add GDDR7 vram name02 AMD / amd-gfx mailing list
[PATCH 0/3] IH v8.0 Support03 AMD / amd-gfx mailing list
[PATCH 0/4] Add NBIF v7.10 Support04 Phoronix
AMD Begins Preparing Open-Source Linux Driver For Graphics Cards With GDDR7
Related
Continue from here
Useful next steps selected from the same technical reference and publication system.
Technical guide
GPU VRAM Capacity Explained: Textures, Resolution, Ray Tracing, Memory Budgets, and Out-of-VRAM Behavior
Understand what GPU VRAM stores, how textures, render targets, resolution, ray tracing, residency budgets, and paging affect capacity pressure, and why VRAM size alone does not determine performance.
Technical guide
GPU Memory Bandwidth Explained: Bus Width, Data Rate, Cache, and Performance
Understand GPU memory bandwidth, including GDDR data rate, bus width, theoretical GB/s, cache effects, VRAM capacity, PCIe bandwidth, and why bandwidth alone does not predict GPU performance.
Technical guide
16 GB vs 32 GB vs 64 GB RAM for Gaming PCs
Choose 16 GB, 32 GB, or 64 GB of system RAM for a gaming PC by measuring the games and simultaneous workloads you actually run instead of relying on a universal capacity rule.
Tool
DDR Memory Latency Calculator
Convert DDR data rate and CAS latency cycles into CAS timing in nanoseconds.