4 ms·
Your comment is highly inaccurate- and in fact is basically straight up Nvidia propoganda. The article you linked to is an article about AMD submitting code for
by bgorman 6y ago
Your comment is highly inaccurate- and in fact is basically straight up Nvidia propoganda. The article you linked to is an article about AMD submitting code for unreleased hardware, which is exactly what you said they are not doing.
I have been using a Polaris based card for years (card released in 2017), and the drivers were submitted in 2016. The kernel drivers were ready at launch and key features like HDMI audio were all working out of the box. Now, you might need to install a modern kernel for everything to work- but that is the Linux way.
It is true that the initial performance was not super great- maybe about 70% of the possible performance, however this was addressed by subsequent improvements to mesa (userspace portion)
AMD has even gone out of their way to support older, obsolete graphics cards that were released before AMD adopted the open source first strategy.
Source:
https://www.phoronix.com/scan.php?page=news_item&px=AMDGPU-Polaris-12 https://www.phoronix.com/scan.php?page=news_item&px=AMDGPU-P...
- loosescrews 6y agoThe difference is the timeline. Basic support landing ~1 month before launch is not acceptable. We barely have a stable kernel with this initial support, and that kernel won't have been picked up by any distributions. Further, for previous AMD hardware releases, this initial support has not been really usable from what I have read. Most of the posts I found on Reddit pointed to it taking several months after launch for the Navi drivers to stabilize. Even then, running a custom kernel in my experience is a lot more trouble than the proprietary Nvidia drivers. Compare to Intel where you have initial basic support landing around 2 years before launch with incremental improvements following. This is the correct way to do open source drivers.