search

abend0c1 / hidrdd

USB Human Interface Device (HID) Report Descriptor Decoder. This will convert a binary or printable hex report descriptor into a C header file. The printable hex can, for example, be an existing C header file - so it can be used to mechanically document an existing report descriptor declaration. The binary report descriptor could, for example, have been extracted from a Wireshark trace of a USB device handshake.
96 stars 15 forks source link

Extract HID Usage definitions from a PDF/JSON spec #7

Open DJm00n opened 1 year ago

DJm00n commented 1 year ago

I noted this text on https://www.usb.org/hid page:

The HID Usage Tables 1.3 document also includes all Usage definitions as a JSON file as an attachment to the PDF. The PDF serves as the 'single' source of truth.

And https://usb.org/sites/default/files/hut1_3_0.pdf have indeed HidUsageTables.json attached. Waratah tool used by USB-IF HID-WG committee have code that extracts that JSON and using it directly.

Maybe RDD! could have such code too instead (in addition to) of manually maintaining rd.conf file?

abend0c1 commented 1 year ago

Thanks Dimitriy, I'll look into that.

I remember suggesting many years ago that they should publish a simple file containing all the known usages (on github maybe) - instead of their ridiculous collection of pdf and text files - but I was ignored, of course. I've been periodically updating rd.conf ever since.

Maybe someone at usb.org has finally seen the light :)