Build2 publishers2 min readPublished
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
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.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- 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.
- 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.
- 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 [5]. For years Linux carried both: Radeon for OpenGL, and AMDGPU, built later for newer cards with Vulkan support [7]. 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 [6].
Moving these cards over took more than flipping a driver binding [11]. 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 [11]. 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 [12].
The roughly 30% figure comes from Phoronix's coverage of Linux 6.19 and the move off Radeon [8]. 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 [1]. 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 [1]. Vulkan titles have no Radeon baseline at all. They go from not running to running [1].
Phoronix writes that AMD has not devoted much in the way of resources to driver work for these cards in years [14]. Dev.to goes further and says the work is carried almost single-handedly by one Valve employee [15]. 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 [16]. Kristóf came from the userspace side, with years on Mesa and a place among the most active RADV contributors [17]. According to dev.to, he described the move into kernel code during the talk as close to a personal experiment [18]. 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 [19].
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.