←back to thread

134 points haunter | 1 comments | | HN request time: 0.206s | source
Show context
shmerl ◴[] No.45271178[source]
What will AMD do with Windows Vulkan driver, didn't they use amdvlk there? There was some radv on Windows experiment, it would be cool if AMD would use that.
replies(1): >>45271289 #
trynumber9 ◴[] No.45271289[source]
No, it was a third driver.

Per AMD

>Notably, AMD's closed-source Vulkan driver currently uses a different pipeline compiler, which is the major difference between AMD's open-source and closed-source Vulkan drivers.

replies(2): >>45271475 #>>45272999 #
shmerl ◴[] No.45271475[source]
Why are they using different compilers?
replies(2): >>45272837 #>>45273335 #
jacquesm ◴[] No.45272837[source]
Bluntly: because they don't get software and never did. The hardware is actually pretty good but the software has always been terrible and it is a serious problem because NV sure could use some real competition.
replies(1): >>45273648 #
AnthonyMouse ◴[] No.45273648[source]
I wish hardware vendors would just stop trying to write software. The vast majority of them are terrible at it and even within the tiny minority that can ship something that doesn't non-deterministically implode during normal operation, the vast majority of those are a hostile lock-in play.

Hardware vendors: Stop writing software. Instead write and publish hardware documentation sufficient for others to write the code. If you want to publish a reference implementation that's fine, but your assumption should be that its primary purpose is as a form of documentation for the people who are going to make a better one. Focus on making good hardware with good documentation.

Intel had great success for many years by doing that well and have recently stumbled not because the strategy doesn't work but because they stopped fulfilling the "make good hardware" part of it relative to TSMC.

replies(2): >>45273955 #>>45274023 #
exDM69 ◴[] No.45274023[source]
> I wish hardware vendors would just stop trying to write software.

How would/should this work? Release hardware that doesn't have drivers on day one and then wait until someone volunteers to do it?

> Intel had great success for many years by doing that well

Not sure what you're referring to but Intel's open source GPU drivers are mostly written by Intel employees.

replies(1): >>45275068 #
1. adrian_b ◴[] No.45275068[source]
The documentation can be published in advance of the product launch.

Intel and AMD did this in the past for their CPUs and accompanying chipsets, when any instruction set extensions or I/O chipset specifications were published some years in advance, giving time to the software developers to update their programs.

Intel still somewhat does it for CPUs, but for GPUs their documentation is delayed a lot in comparison with the product launch.

AMD now has significant delays in publishing the features actually supported by their new CPUs, even longer than for their new GPUs.

In order to have hardware that works on day one, most companies still have to provide specifications for their hardware products to various companies that must design parts of the hardware or software that are required for a complete system that works.

The difference between now and how this was done a few decades ago, is that then the advance specifications were public, which was excellent for competition, even if that meant that there were frequently delays between the launch of a product and the existence of complete systems that worked with it.

Now, these advance specifications are given under NDA to a select group of very big companies, which design companion products. This ensures that now it is extremely difficult for any new company to compete with the incumbents, because they would never obtain access to product documentation before the official product launch, and frequently not even after that.