* Linux Kernel: Microsoft Digital Media Keyboard 3000
@ 2012-07-10 22:53 Jonathan BISSON
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan BISSON @ 2012-07-10 22:53 UTC (permalink / raw)
To: jkosina, dtor, linux-input
Hi,
I've a problem with my Microsoft Digital Media Keyboard 3000 (USB).
One part of the keyboard is seen as a joystick.
I managed to get most keys working by :
blacklisting joydev
adding:
in my udev config:
ENV{ID_VENDOR}=="Microsoft", ENV{ID_MODEL_ID}=="0730", RUN+="keymap
$name 0xc022d zoomin 0xc022e zoomout 0xc01b6 camera 0xc01ab f20"
0xC022D and 0xC022E are zoom in and zoom out keys
0xC01B6 is the camera key
0xC01AB is the Fn-F10 (when disabling the function keys with the special
button switch)
The only one I'm lacking is the 0xC01A2 which corresponds to the «Aero»
key. I can see the scan code when looking in the scancodes given by the
/sys thing, but it's not taken into account. This scancode is not
described neither in the 3.4 kernel source hid-input part. So that can
explain why I can't map this key.
Do I just have to send a patch for adding the corresponding scancode ?
What to do for this part of the keyboard seen as a joydev ?
Thanks for your work on the kernel !
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 2+ messages in thread
* Linux Kernel: Microsoft Digital Media Keyboard 3000
@ 2012-07-11 9:56 Jonathan BISSON
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan BISSON @ 2012-07-11 9:56 UTC (permalink / raw)
To: linux-input, dtor, jkosina
[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]
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.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: lsusb.txt --]
[-- Type: text/plain; charset=UTF-8; name="lsusb.txt", Size: 3173 bytes --]
Bus 002 Device 009: ID 045e:0730 Microsoft Corp. Digital Media Keyboard 3000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x045e Microsoft Corp.
idProduct 0x0730 Digital Media Keyboard 3000
bcdDevice 2.00
iManufacturer 1 Microsoft
iProduct 2 Microsoft® Digital Media Keyboard 3000
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 59
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 60
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 106
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Device Status: 0x0000
(Bus Powered)
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-07-11 9:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-07-11 9:56 Linux Kernel: Microsoft Digital Media Keyboard 3000 Jonathan BISSON
-- strict thread matches above, loose matches on Subject: below --
2012-07-10 22:53 Jonathan BISSON
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).