Re:Vulkan1.3 on the M1 in 1 Month
by astrange on Wednesday June 05, 2024 @09:47PM
(#40592585)
A blog post is different from a real compliant commercial implementation. Other reasons you couldn't do it include eg someone with a patent on it won't license it to you.
[ Parent
| on HN ]
Mesa's implementation will get a compliance certification once it's ready. I don't see why they would have problems with that - other Vulkan drivers got compliance from Khronos once they passed needed tests. Patent FUDs are nonsense - no one else has such issues and many drivers already exist and work fine.
The real reasons are not good at all (i.e. Apple's obsession with lock-in) and have no excuse.
Re:Vulkan1.3 on the M1 in 1 Month
by greenduck1 on Friday June 07, 2024 @06:55AM
(#40607355)
> A blog post is different from a real compliant commercial implementation.
honeykrisp is already a "real conformant" implementation and is listed on Khronos's website already.
https://www.khronos.org/conformance/adopters/conformant-prod...