X Windows ignores the keymap set up at the Linux Kernel level,
and opens the keyboard device in "raw" mode.
To set the mapping for unusual scancodes as provided by
IR remote controls, use the "xev" event viewer to find out
what keycodes X is seeing from the raw keyboard, and then
use "xmodmap" to map those keycodes to keysyms.
That worked for us... best wishes.
Torrey Hoffman
[EMAIL PROTECTED]
> -----Original Message-----
> From: Labhard, MichaelX [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 18, 2001 11:28 AM
> To: '[EMAIL PROTECTED]'
> Subject: [Xpert]setkeycodes
>
>
> All:
>
> We are implementing a TV remote interface to RedHat 7.1. After
> mapping the scan codes with setkeycodes to a key map in the
> default system
> map file, the output from the remote is correct on the
> console (pressing "1"
> outputs "1" just like a keyboard "1"), but an xterm in X
> Windows does not
> see these at all, though it does output a keyboard "1". How
> do we make our
> setkeycodes seen by X Windows? Thanks.
>
> --Michael
>
> _______________________________________________
> Xpert mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/xpert
>
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
