News for hackers. Stuff that matters.
Re:Vulkan1.3 on the M1 in 1 Month by astrange on Wednesday June 05, 2024 @02:32PM (#40588588)
You can't "just support Vulkan", it's too low level. To benefit, the implementation would have to target the GPU specifically since Apple GPUs are different from discrete GPUs.
Re:Vulkan1.3 on the M1 in 1 Month by shmerl on Wednesday June 05, 2024 @06:20PM (#40591278)
Well, Asahi / Mesa developers demonstrated that they can "just support Vulkan" on Apple's hardware as the linked post explains. So Apple never had any excuse for not doing it. Their reasons for sabotaging Vulkan support were always political, not technical.
Re:Vulkan1.3 on the M1 in 1 Month by robertoandred on Wednesday June 05, 2024 @06:31PM (#40591382)
Sabotaging? Metal came before Vulkan.
Re:Vulkan1.3 on the M1 in 1 Month by shmerl on Wednesday June 05, 2024 @06:48PM (#40591530)
How does that stop Apple from supporting Vulkan on their system? It is pure political sabotaging. And you can't pull any excuses like "it requires effort". Apple have pools of cash to do the right thing for users and developers. They simply very intentionally oppose it due to their dinosaur lock-in mentality.
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.
Re:Vulkan1.3 on the M1 in 1 Month by shmerl on Wednesday June 05, 2024 @10:23PM (#40592777)
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...

Re:Vulkan1.3 on the M1 in 1 Month by astrange on Friday June 07, 2024 @02:19PM (#40611377)
You left out a word.
Re:Vulkan1.3 on the M1 in 1 Month by 58028641 on Wednesday June 05, 2024 @08:46PM (#40592250)
https://github.com/KhronosGroup/MoltenVK proves that it is possible, but it is limited by having to go through Metal.
Re:Vulkan1.3 on the M1 in 1 Month by astrange on Wednesday June 05, 2024 @09:50PM (#40592609)
Anything's possible, but it wouldn't be performant. MoltenVK is just about as good as an untuned native Vulkan client would be.
Re:Vulkan1.3 on the M1 in 1 Month by flohofwoe on Thursday June 06, 2024 @03:09AM (#40594429)
If Apple would add native Vulkan support to macOS, it would most likely also go through a Metal "emulation layer" (just like their GL implementation, or the D3D12 implementation in the Game Porting Toolkit).
Re:Vulkan1.3 on the M1 in 1 Month by talldayo on Thursday June 06, 2024 @12:06PM (#40599086)
Because everyone knows from MoltenVK, Metal-based API implementations are just so efficient.