News: 0001587906

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

AMDGPU With Linux 6.19 Will Support Analog Video Connectors For Old GCN 1.0 GPUs

([Radeon] 73 Minutes Ago AMDGPU)


Following last week's [1]initial batch of AMDGPU kernel graphics driver changes intended for Linux 6.19 , another round of new AMDGPU / Radeon / AMDKFD material was sent out today to DRM-Next. Notable with this pull is the Display Core "DC" work for analog video connectors as the initiative from one of Valve's contractors for improving the Radeon GCN 1.0 era GPU support with the AMDGPU driver.

This new batch of AMDGPU changes planned for Linux 6.19 includes the work by Timur Kristóf for enabling display analog encoders within the AMDGPU DC code. This is needed for helping the old GCN 1.0/1.1 era GPUs reach parity to the older Radeon driver with hopes of enabling GCN 1.0/1.1 hardware by default for the modern AMDGPU driver in place of the old Radeon driver code.

Timur the past few months has been working on [2]the analog connector support for AMDGPU DC and with this pull request now appears to all be in place, going along with his other GCN 1.0 Southern Islands and GCN 1.1 improvements this year for the AMDGPU driver. We'll see if in 2026 it finally reaches the point of those older circa Radeon HD 7000 series / Rx 200 series move to AMDGPU by default for enabling better performance, Vulkan with RADV out-of-the-box, and all around a better driver than the older Radeon code primarily for pre-GCN hardware.

This analog connector support is also useful for some Tonga and Hawaii graphics cards that have DVI-I connectors to work with AMDGPU DC.

One of Timur's patches also part of this pull is now enabling DC by default for old Bonaire APUs. Bonaire was an exception due to its presence of analog connector support but otherwise being supported by AMDGPU.

Other material in today's AMDGPU pull request are re-enabling DM idle optimizations, PowerPlay fixes for old Fiji and Iceland GPUs, SR-IOV updates, user queue "UserQ" fixes, adding an Ambient Backlight Management (ABM) KMS property, and various other fixes. More details for those interested via [3]this pull request .



[1] https://www.phoronix.com/news/AMDGPU-Linux-6.19-First

[2] https://www.phoronix.com/news/AMDGPU-DC-Analog-GCN-1.0-1.1

[3] https://lore.kernel.org/dri-devel/20251029205713.9480-1-alexander.deucher@amd.com/


Q: How can I choose what groups to post in? ...
Q: How about an example?

A: Ok. Let's say you want to report that Gretzky has been traded from the
Oilers to the Kings. Now right away you might think rec.sport.hockey
would be enough. WRONG. Many more people might be interested. This is a
big trade! Since it's a NEWS article, it belongs in the news.* hierarchy
as well. If you are a news admin, or there is one on your machine, try
news.admin. If not, use news.misc.

The Oilers are probably interested in geology, so try sci.physics. He is
a big star, so post to sci.astro, and sci.space because they are also
interested in stars. Next, his name is Polish sounding. So post to
soc.culture.polish. But that group doesn't exist, so cross-post to
news.groups suggesting it should be created. With this many groups of
interest, your article will be quite bizarre, so post to talk.bizarre as
well. (And post to comp.std.mumps, since they hardly get any articles
there, and a "comp" group will propagate your article further.)

You may also find it is more fun to post the article once in each group.
If you list all the newsgroups in the same article, some newsreaders will
only show the article to the reader once! Don't tolerate this.
-- Brad Templeton, _Emily Postnews Answers Your Questions on Netiquette_