[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freedesktop-xorg
Subject:    Re: Logitech Media Keyboard
From:       James Cloos <cloos+pdx-xorg () jhcloos ! com>
Date:       2005-04-22 2:29:45
Message-ID: m31x931r3a.fsf () lugabout ! cloos ! reno ! nv ! us
[Download RAW message or body]

>>>>> "Anders" == Anders Johansson <andjoh@rydsbo.net> writes:

Anders> Except the 'Messenger' key. xev reports it as a mouse button,
Anders> for some reason.  Actually two mouse buttons. On key press,
Anders> xev reports button 4 pressed and released, and on key release
Anders> it reports button 5 pressed and released.

That's a fun one.

As you mentioned SuSE, what does showkey(1) report (on the console,
not in X) when you press that key?  Do you get anything in dmesg
when you press it?  2.4 or 2.6 kernel?

You may need to use setkeycodes(8) to have the key send an event that
xkb is happier with.

As an example, on my notebook the play/stop/rew/ff keys map to 0x00 in
the kernel's table, so I use an entry in the inet file that matches
(the hp2505 entry in my case) and these commands at startup:

setkeycodes e001 164
setkeycodes e002 166
setkeycodes e003 165
setkeycodes e004 163

The first arg comes from the kernel log's warning about the unset key
and the latter arg came from trial and error to determine the kernel
to xkb mapping.  (In this case it is 163..166 ==> 153,162,144,164.)

(That mapping is deterministic, just not obvious and hard to track
down in the kernel src.  Having forgotten where it was resorting to
trial and error was actually easier....)

-JimC
-- 
James H. Cloos, Jr. <cloos@jhcloos.com>

[prev in list] [next in list] [prev in thread] [next in thread]