Saitek USB Gamer's Keyboard

Saitek USB Gamer's Keyboard

[Chris Malton]

[-- Attachment #1: Type: text/plain, Size: 715 bytes --]

I have been working on this device for a while, and have come up with 
the following:

The protocol is simple:

?? ?? 52 70 ?? ?? ??
??
KC 1 [DOWN]
?? ?? 52 70 ?? ?? ??

KC	Key
48	1
49	2
50	3
51	4
52	5
53	6
54	7
55	8
56	9
57	Mode A
58	Mode B

The ?? bits represent seemingly random numbers that appear through 
/dev/input/event3, which gets created when the keyboard is plugged in.

I'm in the process of creating a userland application that reads from 
/dev/input/event3 and acts accordingly, based on user preferences.

Should it be the job of the kernel to do the command mapping (and 
subsequently create a virtual keyboard), or should it stay as a 
userland-only program?

I would be intrigued to know.

Chris

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 2146 bytes --]

Re: Saitek USB Gamer's Keyboard

[Jiri Kosina]

On Thu, 17 May 2007, Chris Malton wrote:

> I have been working on this device for a while, and have come up with 
> the following: The protocol is simple:
> ???? 52 70 ?? ?? ??
> ??
> KC 1 [DOWN]
> ?? ?? 52 70 ?? ?? ??

Chris,

is this device a 0x04f2/0x0418? If so, I have already written a patch 
which adds proper mapping of these keys into input events (also see ticket 
#7352 on bugzilla.kernel.org). This patch is queued for next round of 
mainline merge.

-- 
Jiri Kosina