Replies: 1 comment
-
Thanks for posting this. Very interesting! @alyssarosenzweig Wowza! Very impressive work! You rock! And kudos to those working on reverse-engineering the Mx kernels!
The challenge is that Linux on Apple hardware is wide open, including at the hardware level, whereas macOS & iOS are proprietary and very protective. Until that changes, on those platforms, we have to go through the OS and Metal. Having said that, I'm impressed that Honeykrisp managed to make M1 fully Vulkan-conformant. For apps that don't use the App Store, perhaps MoltenVK can get there on macOS by making more use of private API's that map to Honeykrisp functionality. Definitely worth looking into. |
Beta Was this translation helpful? Give feedback.
-
Hi everyone, I noticed this post by Alyssa Rosenzweig: https://rosenzweig.io/blog/vk13-on-the-m1-in-1-month.html
She managed to get a conformant basic Vulkan 1.3 driver running on the Apple M1, calling it Honeykrisp. It doesn't support everything we want yet (transform feedback and such), probably needs a lot of performance optimisation, and probably needs more work to run on M2 and M3 and variants than a Metal-based driver. Also, can a Linux driver even be adapted for use under MacOS?
So what would be the pros and cons of using MoltenVK in an app compared to using Honeykrisp? I can imagine the points above are in play, and I haven't checked licensing (though at least one file is MIT licensed, which is very permissive).
At the very least I hope Honeykrisp could provide inspiration to solve some of the implementation problems that MoltenVK seems to be struggling with..
Beta Was this translation helpful? Give feedback.
All reactions