The open source Vulkan driver for AMD hardware 'radv' now gets 'effectively a pass' for conformance. An awesome milestone for AMD fans.
From the blog post:
They do specifically note that the "Not supported" section isn't missing features, but rather pointless things and stuff the hardware doesn't support.
It still needs to go through the official Khronos Group procedure, so they can't say the driver is actually conforming properly just yet.
I still personally plan to switch to an AMD GPU when the time arises, so it's really pleasing to know that things are in such good shape.
Thanks for the tip Joeri! Article taken from GamingOnLinux.com.
From the blog post:
QuoteTest run totals:
Passed: 109293/150992 (72.4%)
Failed: 0/150992 (0.0%)
Not supported: 41697/150992 (27.6%)
Warnings: 2/150992 (0.0%)
They do specifically note that the "Not supported" section isn't missing features, but rather pointless things and stuff the hardware doesn't support.
It still needs to go through the official Khronos Group procedure, so they can't say the driver is actually conforming properly just yet.
I still personally plan to switch to an AMD GPU when the time arises, so it's really pleasing to know that things are in such good shape.
Thanks for the tip Joeri! Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
Quoting: MayeulCWhile that *might* be true for the kernel (sort of, you can have both amdgpu and radeon enabled for the earlier GPUs, and blacklist one at startup time), RADV and the AMDGPU-PRO (vulkan) driver are using the same kernel module, so there is really no such policy.
I'm not saying that they implemented a system to prevent having two drivers for the same hardware, I'm saying that the maintainers' policy is to refuse patches that would enable two drivers for the same hardware. The idea behind that is to prevent to split the code and the resources in two. So that's why RADV and AMDGPU-PRO can live together: AMDGPU-PRO is not open source, so not in the kernel, so not under this maintainer' policy.
That being said, since these drivers are user space, I might just be saying garbage :D
0 Likes
Good to see such fast progress. I hope optimizations will be the next logical step.
Regarding two drivers. Once AMD will open source their Vulkan implementation, there is really no reason for distros not to provide it as an option. Let the user decide what performs better, radv or AMD Vulkan.
Last edited by Shmerl on 5 May 2017 at 1:43 am UTC
Regarding two drivers. Once AMD will open source their Vulkan implementation, there is really no reason for distros not to provide it as an option. Let the user decide what performs better, radv or AMD Vulkan.
Last edited by Shmerl on 5 May 2017 at 1:43 am UTC
1 Likes, Who?
Patreon
PayPal
See more from me