| 30 | | * The [wiki:windows_backend Windows backend] currently uses Microsoft WinUSB.sys. Support for the libusb0.sys backend (libusb0.sys is the libusb-win32 kernel driver) will be integrated later (#49) as well. |
| 31 | | * Darwin (Mac OS X) has a very different USB driver model when compared with Linux and most UNIXes. It is more like Windows in this area. As a result, although libusb-1.x will build and install on Darwin, many functions are not available. In particular, if the OS has an interface driver that matches the characteristics of a device, it will seize the interface and cannot be detached. So libusb will not be able to use that interface. This is a particular problem with devices, which for Windows/Mac OS programming convenience, identify themselves as HIDs. |
| | 30 | * The [wiki:windows_backend Windows backend] currently uses Microsoft WinUSB.sys. Support for the libusb0.sys backend (libusb0.sys is the libusb-win32 kernel driver) will be integrated later (#49) as well. For generic HID device, [http://www.signal11.us/oss/hidapi/ HIDAPI] is recommended. |
| | 31 | * Darwin (Mac OS X) implementation has one limitation. If the OS has an interface driver that matches the characteristics of a device, it will seize the interface and the kernel driver cannot easily be detached. So libusb will not be able to use that interface. This is a particular problem with generic HID devices. For HID device, [http://www.signal11.us/oss/hidapi/ HIDAPI] is recommended. |
