86166b7bcd
hidraw is an interface that is going to obsolete hiddev one day. Many userland applications are using libusb instead of using kernel-provided hiddev interface. This is caused by various reasons - the HID parser in kernel doesn't handle all the HID hardware on the planet properly, some devices might require its own specific quirks/drivers, etc. hiddev interface tries to do its best to parse all the received reports properly, and presents only parsed usages into userspace. This is however often not enough, and that's the reason why many userland applications just don't use hiddev at all, and rather use libusb to read raw USB events and process them on their own. Another drawback of hiddev is that it is USB-specific. hidraw interface provides userspace readers with really raw HID reports, no matter what the low-level transport layer is (USB/BT), and gives the userland applications all the freedom to process the HID reports in a way they wish to. Signed-off-by: Jiri Kosina <jkosina@suse.cz>
14 lines
281 B
Makefile
14 lines
281 B
Makefile
#
|
|
# Makefile for the HID driver
|
|
#
|
|
hid-objs := hid-core.o hid-input.o
|
|
|
|
obj-$(CONFIG_HID) += hid.o
|
|
|
|
hid-$(CONFIG_HID_DEBUG) += hid-debug.o
|
|
hid-$(CONFIG_HIDRAW) += hidraw.o
|
|
|
|
obj-$(CONFIG_USB_HID) += usbhid/
|
|
obj-$(CONFIG_USB_MOUSE) += usbhid/
|
|
obj-$(CONFIG_USB_KBD) += usbhid/
|
|
|