I'm writing USB HID device firmware and I can get evdev to detect HID keycodes in HID Usage Pages 0x07 (Keyboard/Keypad), 0x01 (Generic Desktop), and 0x0c (Consumer), where the scancode reported by evdev (MSC_SCAN) seems to be `p<<16 | k`, for `p` the Usage Page (specified in the Report Descriptor) and `k` the HID keycode; eg. AC Search has evdev scancode 0xc0201 (HID keycode 0x0201). However I can't get evdev to detect Usage Page 0x10 (Unicode), which is just UCS-2 in the spec (eg. the evdev scancode for `a` in USC-2 should be 0x100061, where the USB device would send 0x61 and the Report Descriptor would be indicate Usage Page 0x10). Perhaps this is because evdev only likes the keycodes in linux/input-event-codes.h? However, /dev/hidraw* sees the Unicode data I'm sending just fine. evdev seems to have no trouble with 16-bit keycodes either, as in the AC Search example above. So can evdev detect keycodes in HID Usage Page 0x10 (and under what Usage)?
