| View previous topic :: View next topic |
| Author |
Message |
madCoder|GN
Tux's lil' helper
Joined: 06 Jun 2003
Posts: 80
|
 Posted: Sat Jul 17, 2004 7:36 am Post subject: atkbd.c and Dell multimedia keyboard |
 |
|
Ok, in kernel 2.4, I found a kernel patch that would adjust the keycodes received by my Dell keyboard's multimedia keys, into a range understandable by the kernel (since by default, its receiveing keycodes greater than 255, which apparently the kernel couldn't handle).
That worked great, and I was able to use acme to map those keys to their respective functions. The problem now is that I've upgraded to the 2.6 kernel (2.6.7), and obviously the same patch would not work, and I can't seem to figure out how to edit atkbd.c to make the kernel understand those keycodes.
Before starting X, at the console, if I run 'showkey' in keycode mode, it will recognize each of my multimedia keys, reporting this for the multimedia keys: | Quote: | keycode 261 press
keycode 261 release
keycode 262 press
keycode 262 release
keycode 263 press
keycode 263 release
etc... |
But running showkey in scancode mode, it does not recognize any of those keys (presumably because the keycode is > 255). I haven't tried yet, but I am pretty sure that I can't just use loadkeys or setkeycodes, since loadkeys will only accept up to 255 for the keycode, and setkeycodes expects a scancode to assign to a keycode, which won't help me because I can't read the scancode that it's receiving. By the way, running 'xev' in X produces no response when pressing the multimedia keys. The only non-standard key that is recognized and does work is the Sleep key, which I can assign in the Gnome 2.6 keyboard control panel.
Although I don't know if it helps, it might be interesting to note that if I 'cat /dev/input/event1' and press the multimedia keys, it responds for each keypress (and does not respond to any normal keys other than those), whereas event0 responds to the rest of the keyboard. I don't know what significance that has, but the whole problem is quite annoying 
Does anyone know how I can modify atkbd.c (or another method) to transpose those keys into a usable range that the kernel, showkey, and ultimately X will be able to understand and use?
_________________
madCoder <madCoder@gamesurge.net>
Abuse Manager
http://www.gamesurge.net/ |
|
| Back to top |
|
 |
madCoder|GN
Tux's lil' helper
Joined: 06 Jun 2003
Posts: 80
|
| Posted: Mon Aug 02, 2004 4:13 am Post subject: |
|
|
Any ideas on how I can transpose those scancodes so that the kernel will recognize my multimedia keys?
_________________
madCoder <madCoder@gamesurge.net>
Abuse Manager
http://www.gamesurge.net/ |
|
| Back to top |
|
|
firephoto
Veteran
Joined: 29 Oct 2003
Posts: 1612
Location: +48° 5' 23.40", -119° 48' 30.00"
|
| Posted: Thu Sep 02, 2004 2:28 am Post subject: |
|
|
I'm looking for the same or a similar solution for a Logitech MX Duo Y-RJ20. There are 17 keys that have keycodes higher than 255. All the secondary function F-keys plus scroll click, Messenger-SMS, Webcam, iTouch, and the Shopping buttons. These show as events with evdev on the same event interface as the mouse when I "cat /dev/input/event3".
Why does the kernel not assign scancodes to keys over 255? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
