We are maintaining two different, unrelated kernel extensions for SATA devices, one codeless and one with code. The first one matches to AppleAHCIDiskDriver and the latter one deals with IOSCSIBlockCommandsDevice, IOSCSIPeripheralDeviceType00 and IOBlockStorageDevice, implementing a SCSI-ATA S.M.A.R.T attribute passthrough client.
I have some questions regarding deprecation and a path forward for us:
Which of these kexts would be deprecated going forward? I don't see any mentions of storage drivers, does that mean they are not deprecated? Would the S.M.A.R.T driver fall on the fact that it uses IOSCSI?
The docs mention "In the few cases where your driver requires a kernel extension, use a
codeless kext to match your hardware to the existing system driver". Does that mean that codeless kexts in general are not deprecated?
Is there anything in DriverKit to enable interaction with IOBlockStorageDevices over USB?
Cindori
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
On macOS 13 Beta with Xcode Beta 4, I'm unable to use the ARView Rendering options described in the documentation:
https://developer.apple.com/documentation/realitykit/arview/renderoptions-swift.property?changes=latest_major
They simply don't exist on the ARView class. How can we disable rendering effects on macOS? A simple cube uses 1GB of memory which is a bit ridiculous.
Furthermore, there should be a way to control the frame rate of the view. It's forced to 120hz on my Macbook which is way overkill.
When reverse engineering RealityKit, I can see that there is a variable there:
RealityKit.ARView.__preferredFrameRate.getter : Swift.Float
But it's private. Any plans to make this a public setting?