Hi,


I've a problem with my Microsoft Digital Media Keyboard 3000.

One part of the keyboard is seen as a joystick by the hid layer of the
kernel (creating a js0 node with udev…)

The lsusb output is in the attachements.


as you can see inside it, the keyboard declares two interfaces:
bNumInterfaces          2


One with :
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      1 Keyboard

which seems ok

and one with:

      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None

The device is cut in two by event system :
pci-0000:00:1d.7-usb-0:1.2:1.0-event-kbd
pci-0000:00:1d.7-usb-0:1.2:1.1-event-kbd

but this last one is also provided to :
pci-0000:00:1d.7-usb-0:1.2:1.1-kbd -> ../js0

The signals sent on it are nothing like a joystick (some garbage
sometimes, but nothing that seems coherent).

Special keys seems to be sent only to the second input event device. But
I managed to get them working by remapping them :
/usr/lib/udev/keymap input/event11 0xc022d back 0xc022e forward 0xc01b6
camera 0xc01a2 f19

the only one which is not working is the "Aero" key, giving a scancode
of 0x1A2, I can see it in the /sys/kernel/debug/hid/…/event but it
doesn't seems to be declared as a valid scancode judging by what I see
in include/linux/input.h of a 3.4 kernel.

Do you think it can be possible to avoid the kernel seeing this as a
joystick (joydev module) and to add this 0x1A2 scan code ?


If you need any further information, I may provide them to you.


Thanks for your work on the kernel.