464 key - additional information
Lokean Darken
lokean.darken at gmail.com
Mon Jan 26 16:06:07 PST 2009
Hello, thank you for reply
On Tue, Jan 27, 2009 at 12:52 AM, Sébastien Mazy <melyadon at gmail.com> wrote:
> Hi Michal,
>
> On Tue, Jan 27, 2009 at 12:39:20AM +0100, Lokean Darken wrote:
> > This is my fdi which I use to remap key 464 to key 216
> >
> <snip>
> >
> > Anyway, xev still don't catch any signal while I press this key...
> >
> > Is this configuration right? If yes, how should I found where is the
> > problem?
>
> 1) make sure your fdi file is under /etc/hal/fdi/policy, so that it is
> processed after the ones from your distribution
Yes, fullpath is /etc/hal/fdi/policy/30-n810.fdi
>
>
> 2) is 0x1d0 really the scancode from the key? How did you find it?
To be honest, I can't swear. I used hexadecimal form of 464 and in
/usr/include/linux/input.h is such key defined as:
#define KEY_FN 0x1d0
Then I guessed it's ok. Unfortunelly, I have no access to real console for
this device, only over X or by ssh, so I don't know howto make better guess.
>
>
> 3) what returns lshal -m when you press the key?
>
Nothing, no matter what key I press, there is no output.
>
> --
> Sébastien Mazy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freedesktop.org/archives/hal/attachments/20090127/ef382525/attachment.htm
More information about the hal
mailing list