Changes between Version 2 and Version 3 of FAQ


Ignore:
Timestamp:
01/06/11 19:52:50 (2 years ago)
Author:
stuge
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FAQ

    v2 v3  
    2020Besides the USB protocol restrictions, using the HID class is much more inconvenient on systems other than Windows. For what is probably historical reasons, the generic file-like API exposed by the Windows HID class-specific driver is unique. On other systems, the HID class driver does not offer a similar simple generic API. 
    2121 
    22 If the broadest platform compatiblity is important (this may be why you look toward libusb in the first place) then a much more neutral alternative is to use a vendor-specific device class. This requires that a device-specific kernel driver be installed on Windows, but that process can be automated completely using [wiki:libwdi]. 
     22If the broadest platform compatiblity is important (this may be why you look toward libusb in the first place) then a much more neutral alternative is to use a vendor-specific device class. This requires that a device-specific kernel driver be installed on Windows, but that process can be automated completely using [wiki:libwdi], and on all other systems supported by libusb there is no need for any interaction at all with kernel drivers or the driver model.