Hacker Neue

Preferences
trws parent
You have this largely right, but I need to defend the Radeon driver a bit here. The driver that caused all the problems was the proprietary fglrx driver, not the open source Radeon driver. The issue with the Radeon driver wasn’t stability, it was that it was 2d acceleration only.
tremon
it was 2d acceleration only

Not completely true either, it eventually supported most of the normal 3d primitives but gaming performance was never a priority because there were few developers and they weren't employed by AMD/ATI -- which also meant that some cards would only reach full feature support after their EOL, sadly.

The amdgpu also driver benefits from a lot of the groundwork that has been done since. The radeon driver is older than kernel features like KMS (kernel modesetting) and GEM (graphics execution manager), and the LLVM-based shader compiler in mesa (userspace). I'd say that the radeon driver was actually the proving ground for many of these features, because it was the most capable open source 3d driver: The Intel 845/915 hardware barely supported 3d operations, and the only 3d-capable open source driver for Nvidia was the reverse-engineered nouveau driver.

Luckily, many people working on the amdgpu driver are actually on AMD's payroll these days.

account42
AMD had developers working on radeon (the older open source kernel driver) and radeonsi (the open source user-space OpenGL driver backend for newer cards in Mesa that now sits on top of amdgpu) before the switch to amdgpu (the newer open source kernel driver). While the kernel driver isn't irrelevant for performance, it depends more on the user space portion (radeonsi and r600 before that) which was kept with the amdgpu switch. What the amdgpu driver brought is more sharing of display code with their windows drivers. The main difference in performance is between r600 (mostly developed without financial support from AMD) and radeonsi (mostly developed by AMD). Of course these days the most relevant user-space portion is radv (open source Vulkan driver in Mesa) which is NOT developed by AMD but rather funded by Valve (and at least initially Red Hat). There is also the open source amdvlk Vulkan user-space driver developed by AMD which is the same as their proprietary Vulkan driver except with the proprietary shader compiler swapped out for the same LLVM backend that radeonsi uses. And if this all wasn't confusing enough, AMD also calls the full driver package with the proprietary Vulkan driver and some snapshot of the open source OpenGL Mesa drivers (radeonsi) "amdgpu-pro".
chao-
I remember! I stand corrected on the name and the issues!

I forgot that name "fglrx", probably a mental self-defense mechanism. Those were some bad times, trying to get different display outputs to work at the same time, guessing and testing values in xorg.conf, so on. There was some community utility someone wrote to try and help with installation, reinstallation, configuration and reconfiguration, but the name eludes me now.

I would edit my post to correct it, but it seems the edit window has passed.

This item has no comments currently.