d7cdc3c29e
t_usbhid/check_hid_get_data has been failing since it existed, mark as such
2016-08-17 12:10:42 +00:00
f9e98a931a
Don't crash when the device's HID Report Descriptor Pops from an empty stack.
2016-01-07 16:10:49 +00:00
4887406fba
Add tests for HID Parser Pop-on-empty-stack bug.
2016-01-07 15:58:23 +00:00
43fe984867
Move libusbhid tests' Report Descriptors and Report Data to seperate file,
...
so future tests of the kernel HID functions can use them too.
2016-01-04 22:07:16 +00:00
cf34dae03a
reorganize constant test data
2016-01-03 15:26:39 +00:00
25812d50a0
Move MY*_ATF_CHECK_EQ debugging helper macros to before all functions.
2016-01-03 15:16:10 +00:00
aaf9a4516d
Teach hid_parse_usage_in_page() how to understand hex literals, in
...
addition to the usual table lookup.
2016-01-02 01:24:44 +00:00
f5863ab3d2
Fix round-trip of hid_usage_in_page(hid_parse_usage_in_page()) when
...
the usage is a catch-all format string.
This should allow usbhidctl(1) to understand an item argument of
"Button:Button_65535".
2016-01-02 01:04:15 +00:00
f8f5861113
Rework unsigned range test cases.
...
If the USB HID 1.11 spec is interperted to the letter, there's no such
thing as a unsigned Logical/Physical Minimum/Maximum. When the (signed)
Minimum is greater than the (signed) Maximum, it's a possibility that
the device is attempting to present unsigned report data.
2016-01-01 23:46:04 +00:00
c8b0c3452c
Fix hid_get_data() for negative or 32-bit report data.
2016-01-01 22:59:12 +00:00
bc1f6fc421
value debugging for the Logical/Physical range checks
2016-01-01 22:47:34 +00:00
3a26fec827
tests for libusbhid (many of which fail)
2016-01-01 21:38:53 +00:00
jakllsch