You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
bInterfaceNumber is expected to return the `%02x` format according to the current kernel sources. Even if that is not true, a user can always manually specify the hidraw device if the wrong device is detected.
|1 year ago|
|udev||1 year ago|
|.gitignore||9 years ago|
|Makefile||8 years ago|
|NEWS||1 year ago|
|README.txt||8 years ago|
|hidpp20.c||8 years ago|
|hidraw.c||8 years ago|
|keyboard.txt||9 years ago|
|ltunify.c||1 year ago|
|notes.txt||9 years ago|
|read-dev-usbmon.c||9 years ago|
|registers.txt||8 years ago|
|shell||8 years ago|
|usbmon-setperms||8 years ago|
|usbmon.awk||9 years ago|
Logitech Unifying tool for Linux
See also the article on <https://lekensteyn.nl/logitech-unifying.html>
I have learned a bit from the kernel source code hid-logitech-dj, but the
"official" Logitech specification (HID++ 1.0) was much more useful. These
documents can be found on <https://lekensteyn.nl/files/logitech/>.
usbmon.awk - initial debugging tool used for tapping usbmon from debugfs
hidraw.c - successor of usbmon.awk that can parse packets of usb payload.
read-dev-usbmon.c - Reads data from /dev/usbmonX and show interpreted data in a
more human-readable way.
Note: as a quick-n-dirty hack, I included hidraw.c at some point into the
read-dev-usbmon program. Otherwise, I had no way to show the difference between
a send or receive packet without adding to the same stdout stream. If I included
it in the stderr pipe, then it would be interleaved with stdout in an
unpredictable manner. This means that hidraw.c is currently unusable, it does
not process data correctly.