Skip to content

Build Independently confirmed2 publishers 2 min read Published Updated

Linux support for AMD's decade-old GCN Radeons rests largely on one Valve engineer

Valve's Timur Kristóf moved AMD's GCN 1.0/1.1 Radeons onto the AMDGPU kernel driver, opening RADV Vulkan and a roughly 30% speedup on decade-old cards. AMD has invested little in these cards for years, so their kernel upkeep now depends almost entirely on one engineer on Valve's payroll.

The Engineer · Build desk

Send a correction

What happened

  • Kristóf presented the year of kernel work at the X.Org Developer's Conference, XDC 2026, in Toronto on October 3, 2026.
  • The affected parts are AMD's first two GCN generations, launched in 2012 and 2013 in cards such as the Radeon HD 7000 and R9 series.
  • Along the way he fixed defects in AMDGPU's display code for these cards and inherited power management problems, then added soft reset support.
  • According to dev.to, the roughly 30% gain seen with Linux 6.19 came before the fixes Kristóf presented at XDC this year.

Why it matters

  • What's now possible capability GCN 1.0/1.1 owners can now try Steam titles that require Vulkan, Proton games included, on hardware that was limited to OpenGL while it sat on the Radeon driver.
  • Who's exposed exposure Further kernel fixes for these cards depend on Valve keeping one engineer assigned to them, because AMD has spent little on this hardware line for years.
  • What it sets up precedent With Valve's paid team now working in AMDGPU kernel code as well as Mesa, kernel gaps that affect Steam on older AMD hardware are likelier to be fixed by Valve, on Valve's priorities.

The kernel driver decides which userspace drivers a card can reach. RADV, Mesa's Vulkan driver, only talks to AMDGPU, and no equivalent layer was ever written for the legacy Radeon driver [11]. For years Linux carried both: Radeon for OpenGL, and AMDGPU, built later for newer cards with Vulkan support [16]. A GCN 1.0 or 1.1 card bound to Radeon was held to OpenGL through radeonsi. Most modern games that need Vulkan were out of reach, including the ones Steam runs through Proton [12].

Moving these cards over took more than flipping a driver binding [3]. The display work was in the modesetting code, the subsystem that drives video output, and dev.to reports the defects there had gone untouched for years [3]. Soft reset is the part I would single out as good engineering. It lets the GPU recover from a graphics fault without restarting the whole machine [4].

The roughly 30% figure comes from Phoronix's coverage of Linux 6.19 and the move off Radeon [13]. The reports here do not say which cards or games produced it. A before-and-after comparison against Radeon can only use workloads that ran on Radeon. Per dev.to, that means OpenGL through radeonsi [21]. For the number to carry over to a given machine, that machine has to be a GCN 1.0/1.1 part running OpenGL work that resembles the test suite [21]. Vulkan titles have no Radeon baseline at all. They go from not running to running [21].

Phoronix writes that AMD has not devoted much in the way of resources to driver work for these cards in years [6]. Dev.to goes further and says the work is carried almost single-handedly by one Valve employee [8]. Valve runs one of the few paid teams on the Linux graphics stack. Its focus is Mesa, and for about a year it has covered AMDGPU as well [9]. Kristóf came from the userspace side, with years on Mesa and a place among the most active RADV contributors [18]. According to dev.to, he described the move into kernel code during the talk as close to a personal experiment [19]. It turned into months of sustained work [20].

I think the engineering here is sound and the port was worth doing. The talk also covered how Kristóf got into AMDGPU kernel development, pitched at anyone who wants to work on the open-source AMD kernel driver [15].

What to watch

  • Whether AMD engineers or new outside contributors start reviewing and extending the GCN 1.0/1.1 AMDGPU code after the talk's section on getting involved.
  • Fresh benchmarks on a kernel carrying Kristóf's display, power management and soft reset fixes, which would show what this year's work adds on top of the Linux 6.19 gain.
  • Whether Valve keeps AMDGPU kernel work in its paid graphics team's remit beyond the first year.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence55
Adoption35
Hype gap+20
Incentives60
Confidence55
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Kristóf transitioned AMD GCN 1.0/1.1 graphics cards and APUs from the legacy Radeon kernel driver to the modern AMDGPU kernel driver.

    Reported Supported Source: PhoronixView cited source
  2. [2]

    Kristóf addressed defects in the AMDGPU display code for these legacy cards and various power management issues, then added soft reset support and other enhancements.

    Reported Supported Source: PhoronixView cited source
  3. [3]

    Migrating a card from Radeon to AMDGPU was not just changing a name in the kernel; Kristóf had to review the modesetting code (the subsystem handling video output) for these GPUs, where he found defects nobody had touched in years.

    Reported Supported Source: dev.toView cited source
  4. [4]

    Soft reset is a function that lets the GPU recover from a graphics error without restarting the whole machine.

    Reported Supported Source: dev.toView cited source
  5. [5]

    Timur Kristóf, an engineer on Valve's graphics team, presented his work modernising AMDGPU for GCN cards at XDC 2026 in Toronto on October 3, 2026.

    Reported Supported Source: dev.toView cited source
  6. [6]

    AMD has not devoted much resources to driver improvements for these aging graphics cards in years.

    Reported Supported Source: PhoronixView cited source
  7. [7]

    Valve published the PDF slides and the full recording of the presentation.

    Reported Supported Source: dev.toView cited source
  8. [8]

    Because AMD has not invested in these cards for years, the work is sustained almost single-handedly by a Valve employee.

    Reported Supported Source: dev.toView cited source
  9. [9]

    Valve maintains one of the few paid teams working on the Linux graphics stack, focused on Mesa and, for the past year, also on AMDGPU.

    Reported Supported Source: dev.toView cited source
  10. [10]

    The move to AMDGPU unlocks the RADV Vulkan driver, better performance and better functionality than the legacy Radeon code.

    Reported Supported Source: PhoronixView cited source
  11. [11]

    RADV, Mesa's Vulkan driver, only talks to AMDGPU; an equivalent layer was never written for the old Radeon driver, so the legacy Radeon driver never had access to RADV.

    Reported Supported Source: dev.toView cited source
  12. [12]

    While a GCN 1.0/1.1 card ran on Radeon, it was limited to OpenGL via radeonsi, without most modern games that require Vulkan, including those running through Proton on Steam.

    Reported Supported Source: dev.toView cited source
  13. [13]

    Linux 6.19 showed a roughly 30% performance boost for old AMD Radeon GPUs from transitioning them to AMDGPU.

    Reported Supported Source: Phoronix, citing its own Linux 6.19 coverageView cited source
  14. [14]

    The roughly 30% improvement with Linux 6.19 came before the fixes Kristóf presented this year.

    Reported Supported Source: dev.toView cited source
  15. [15]

    The presentation covers Kristóf's experience getting involved in AMDGPU kernel driver development, for those who may want to get involved with open-source AMD Linux kernel driver development.

    Reported Supported Source: PhoronixView cited source
  16. [16]

    For years Linux supported these GPUs with two drivers in parallel: the old Radeon driver, designed for OpenGL, and AMDGPU, built later to cover newer cards with Vulkan support.

    Reported Supported Source: dev.toView cited source
  17. [17]

    GCN 1.0 arrived in 2012 and GCN 1.1 in 2013, in cards such as the Radeon HD 7000 and R9 series.

    Reported Supported Source: dev.toView cited source
  18. [18]

    Before this project Kristóf spent years working in userspace on the Mesa graphics driver and was among the most active contributors to RADV and Mesa.

    Reported Supported Source: dev.toView cited source
  19. [19]

    During the talk, Kristóf described getting into the kernel as almost a personal experiment.

    Reported Supported Source: dev.to (paraphrase of the talk, not a direct quotation)View cited source
  20. [20]

    The move into AMDGPU development started almost as a personal experiment to understand how the kernel and userspace coordinate, and became months of sustained work.

    Reported Supported Source: dev.toView cited source
  21. [21]

    Any Radeon-versus-AMDGPU comparison could only use workloads that ran on the Radeon driver, which per dev.to means OpenGL through radeonsi; Vulkan titles had no Radeon baseline and go from not running to running, so the 30% figure transfers only to similar OpenGL workloads on GCN 1.0/1.1 parts.

    Derived Supported

Sources

2 independent publishers whose own reporting we read for this story.

  1. dev.to

    2 articles · October 5, 2026

    Valve moderniza el driver AMDGPU para GPU AMD GCN de hace una década
  2. phoronix.com

    1 article · October 3, 2026

    The Amazing Work By Valve's Timur Kristóf On Improving Old AMD GPUs On Linux

Topics and entities

Topics

  • Linux graphics drivers
  • Hardware longevity

Entities