On Tue, 23 Jun 2009, Janusz Krzysztofik wrote: > > You can either unbind HID driver from the device completely, and write your > > own userspace driver using libusb. > > Or you can patch the HID driver not to attach this device to inpu subsystem, > > and only trigger creation of /dev/hidraw (or /dev/hiddev respectively), and > > write user-space application that will process the HID events from these > > device nodes, and process them in your application as needed. > I thouhgt this could be done from userspace without any kernel modification, > just the way "input-events -g" does it. Am I missing anything? Calling ioctl(EVIOCGRAB) is of course another possibility, if you are perfectly fine with the work HID driver does and don't need any modifications there (i.e. no changes in usage parsing, etc). -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
