diff options
author | Jiri Kosina <jkosina@suse.cz> | 2007-05-14 09:57:40 +0200 |
---|---|---|
committer | Jiri Kosina <jkosina@suse.cz> | 2007-10-14 14:47:26 +0200 |
commit | 86166b7bcda0bcb53525114fa1c87ac432be478e (patch) | |
tree | 1f6afc4c1c1d7a6dd88236f3c11fde61c1885b14 /include/linux/icmp.h | |
parent | efc493f9d5463d933a64a2758fbe6d9bb8300cbb (diff) | |
download | kernel-crypto-86166b7bcda0bcb53525114fa1c87ac432be478e.tar.gz kernel-crypto-86166b7bcda0bcb53525114fa1c87ac432be478e.tar.xz kernel-crypto-86166b7bcda0bcb53525114fa1c87ac432be478e.zip |
HID: add hidraw interface
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>
Diffstat (limited to 'include/linux/icmp.h')
0 files changed, 0 insertions, 0 deletions