|
On 12/1/2017 11:24 AM,
[email protected] wrote:
Hi James, It sounds like the device isn’t sending (or isn’t being asked for any) input reports when plugged in on boot. Also, if the device implements BOOT protocol then EFI is likely to talk to it as well.Are you able to capture a bus trace for this issue? —scott I'm afraid I have no idea what a bus trace is or how to capture one. On Nov 30, 2017, at 9:34 AM, James Walker <[email protected]> wrote: I'm using the IOHID APIs to communicate with USB game controllers. I subscribe to device added/removed notifications, and when I get a notification that a new device is available, I subscribe to value notifications like this: IOHIDDeviceScheduleWithRunLoop( device, CFRunLoopGetMain(), kCFRunLoopDefaultMode ); IOHIDDeviceRegisterInputValueCallback( device, ValueCallback, context ); IOHIDDeviceOpen( device, kIOHIDOptionsTypeNone ); The problem: if the game controller was plugged in when the Mac booted up, I get the device added callback, but the value callback is never called. As soon as I unplug the device and plug it back in, the value callback starts working. Is there something I can do to fix this, or is it a hardware issue? |
_______________________________________________ Do not post admin requests to the list. They will be ignored. Usb mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/usb/archive%40mail-archive.com This email sent to [email protected]
