Comment 3 for bug 325581

The reason evdev is confused is that, apparently, ioctl(fd, EVIOCGBIT, EV_KEY, ...) is returning capabilities that don't match the actual device in question. (Come to think of it, EV_ABS coming back with something for a mouse is odd, too.)

I'm not sure if the right solution is to add something to the quirks list in the kernel usbhid stuff, and/or if a workaround in evdev would be useful.

Would something like the attached help? (Still trying to figure out how to build it myself so I can test...)