RadeonHD Driver Switches To AtomBIOS
A month ago we had shared that the RadeonHD driver would be switching to AtomBIOS, or the ATI video BIOS abstraction layer used since their R400 series graphics cards, and today they have completed this code merger. The Novell developers behind the RadeonHD driver have long preferred the route of banging on the registers directly than relying upon this closed-source (aside from the open-source parser) framework, but they had folded due to pressure from AMD with the time it's taken to support new GPUs and the developers behind held up waiting on register documentation to arrive.
For the past month this AtomBIOS-ized version of the xf86-video-radeonhd driver have lived in a separate development branch, but today more than one hundred patches have been merged to master. Now by default the driver will be using AtomBIOS.
A number of the R500 and R600 graphics cards though have hard-coded mode-setting support that was done over the past year, but not all of that work has gone to waste. Where there is a hard-coded path, the RadeonHD driver will still use it unless the user sets the UseAtomBIOS option within their xorg.conf. For all other chipsets, AtomBIOS is used by default.
Next up will be to merge the HDMI audio and Command Submission driver branches to master.
For the past month this AtomBIOS-ized version of the xf86-video-radeonhd driver have lived in a separate development branch, but today more than one hundred patches have been merged to master. Now by default the driver will be using AtomBIOS.
A number of the R500 and R600 graphics cards though have hard-coded mode-setting support that was done over the past year, but not all of that work has gone to waste. Where there is a hard-coded path, the RadeonHD driver will still use it unless the user sets the UseAtomBIOS option within their xorg.conf. For all other chipsets, AtomBIOS is used by default.
Next up will be to merge the HDMI audio and Command Submission driver branches to master.
5 Comments