Change in keycodes generated by the keyboard

[jj . iglesias]

Hi all!

I've got a Microsoft Wireless Natural Multimedia keyboard (it was a
gift...) and I've been using its "extra" keys upto the 2.6.9 (maybe 2.6.10,
I'm not sure!) version of the kernel. I use to update the kernel as
frequently as I can and one day I noticed that these extra keys didn't work
any more.

When I was given the keyboard I started to make it work under my linux, and
thus I used tools such as "showkey" and I learnt the differences between
scancodes, keycodes or at least I tried to learn them.

Well, I've found that the last revisions of the 2.6 kernel have changed the
keycodes generated by the keyboard. There are "short" keycodes such as
0x1a, "extended normal" keycodes such as "0x008102" (I'm writing at my
work, trying to remember the structure of the keycode, but the point is in
the "81"); and "extended anormal" keycodes that are similar to the previous
but they include "82".

These last keycodes are not sensed by any application, mainly X. I remember
that previous revisions of the 2.6 kernel had sixteen places empty in
certain array used to convert from keycodes to scancodes. The kernel, then,
complainted saying that "keycode 240 has no scancode" or something... I
filled the array with scancodes that weren't in use and the extra keys
begun to work.

But now (that array continues having sixteen empty spaces) the keycodes
generated by the keyboard are completely different.

Any help? Any capture that I could do and email it?

Thanks in advance.
Regards.

Jose Juan Iglesias.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/