Charles Lepple wrote: > hid_force_open() is simply a wrapper for the > libusb_detach_kernel_driver_np(), and hid_interrupt_read() > is just some parameter conversion and error checking for > libusb_interrupt_read(): .. > You could probably implement what you need in a dozen lines or so > by calling libusb directly.
I'd recommend HIDAPI over libusb. > I haven't tried HIDAPI that Peter mentioned, but it sounds like it > might offer a more portable solution. Indeed. With libusb there is still the matter of kernel drivers. The Windows support in libusb-1.0 tries to fake it on top of the HID API but I don't really think that's a good approach. HIDAPI on the other hand is tailored specifically for HID, on Win Mac Linux, works *with* the kernel drivers instead of against them, is simpler (less generic) than libusb, and I think the best solution for byte level communication with HID class devices. //Peter _______________________________________________ libhid-discuss mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss http://libhid.alioth.debian.org/
