iokit

Migrating from codeless KEXT to DEXT. Usb interfaces disappeared

杀马特。学长 韩版系。学妹 提交于 2020-08-19 10:38:29
问题 I'm trying to migrate from KEXT to DEXT. My USB device should not be matched by the classic driver (in the other case, it does not allow to open the device and interface). I am using a sample USB application for testing. So, before installing the system extension, I was able to see 1 device and 3 interfaces. However, when I install the system extension (next), I can not find any interfaces. They seem to be lost. To search for interfaces I use the command “ioreg -lirc IOUSBHostInterface”. Any

Performance issue after migrating from codeless KEXT to DEXT

混江龙づ霸主 提交于 2020-08-08 06:08:32
问题 I am working on migrating a codeless KEXT to DriverKit. It is used to disable the IOKit HID driver for USB devices that present themselves as HID compliant in firmware upgrade mode. So far I have managed to match an empty subclass of IOService to the relevant devices. Here's an example of the IOKitPersonalities entries I'm using: <dict> <key>CFBundleIdentifier</key> <string>$(PRODUCT_BUNDLE_IDENTIFIER)</string> <key>CFBundleIdentifierKernel</key> <string>com.apple.kpi.iokit</string> <key

Performance issue after migrating from codeless KEXT to DEXT

无人久伴 提交于 2020-08-08 06:08:11
问题 I am working on migrating a codeless KEXT to DriverKit. It is used to disable the IOKit HID driver for USB devices that present themselves as HID compliant in firmware upgrade mode. So far I have managed to match an empty subclass of IOService to the relevant devices. Here's an example of the IOKitPersonalities entries I'm using: <dict> <key>CFBundleIdentifier</key> <string>$(PRODUCT_BUNDLE_IDENTIFIER)</string> <key>CFBundleIdentifierKernel</key> <string>com.apple.kpi.iokit</string> <key

How should “NewUserClient” be implemented

倾然丶 夕夏残阳落幕 提交于 2020-08-03 09:11:23
问题 I am trying to interact with a dext from an application. I am able to find the service using IOServiceOpen and I get a call to NewUserClient of my dext (I can see the type parameter passed being output in the log). After this I am a bit lost. Reading here about NewUserClient I can see that one should use Create to create a new Service object. The Discussion part here says The keys in the propertiesKey dictionary describe the new service. Should this dictionary be placed in the plist file for

Creating virtual USB device in Mac OS X

北慕城南 提交于 2020-08-02 05:05:55
问题 I tried to add virtual usb device with driver in Mac OS programmatically. IOKit documentations says: Traditionally, drivers of virtual devices match on IOResources because virtual devices do not publish nubs of their own. Another example of such a driver is the HelloIOKit KEXT (described in “Creating a Device Driver with Xcode”) which matches on IOResources because it does not control any hardware. But I don't found way to add virtual device in system. How can I do that? 回答1: What are you

How to set `com.apple.developer.driverkit.transport.usb` entitlement?

风格不统一 提交于 2020-07-01 15:49:30
问题 I am unsure about how to set the com.apple.developer.driverkit.transport.usb key in my dext entitlements file. The Info.plist file already contains the IOKitPersonalities dictionary, and reading about the com.apple.developer.driverkit.transport.usb dictionary it looks like it should contains entries with the same information as the entries of IOKitPersonalities . The entitlements file for a project that is very similar to what is being shown in the WWDC video about driver kit sets this to:

How to set `com.apple.developer.driverkit.transport.usb` entitlement?

≡放荡痞女 提交于 2020-07-01 15:47:29
问题 I am unsure about how to set the com.apple.developer.driverkit.transport.usb key in my dext entitlements file. The Info.plist file already contains the IOKitPersonalities dictionary, and reading about the com.apple.developer.driverkit.transport.usb dictionary it looks like it should contains entries with the same information as the entries of IOKitPersonalities . The entitlements file for a project that is very similar to what is being shown in the WWDC video about driver kit sets this to: