3 ms·
Having written system extensions (both kext and DriverKit), that seems more like an issue with the extension itself.
by Klonoar 5y ago
Having written system extensions (both kext and DriverKit), that seems more like an issue with the extension itself.
- indymike 5y agoThat may, but Apple broke a formerly working API. If Google can't figure it out, that's a signal.
- Klonoar 5y agoI mean... no? If you're referring to the Kext/DriverKit changeover, this is just false - Kexts still work in Big Sur, they're just trying to slowly shift the ecosystem to DriverKit. Nothing has truly changed there yet. If you're referring to a broken thing within Kexts/IOKit itself, that would be a pretty severe bug that would get attention within Apple. I feel confident saying this as I've reported bugs like this and they get appropriate priority levels. Lastly, if you're writing (signed) driver code, you generally have access to resources within Apple to get answers to questions. I'm not even a large company and it was relatively easy to get in touch with those teams - and this stands in contrast to other teams within Apple.