|
midrange.com
Phillip.Watts@xxxxxxxxx writes:
> But when I go to X and do xev, it reveals the old garbage mapping.
> Aaaah! X does not use the kernel scancode to keycode map !
No. It puts the keyboard into RAW mode, or it wouldn't be able to
detect separate key up and down events, or anything at all for
Control, Alt, etc.
> Nowhere can I find out how to deal with scancodes in X without going into the
> source. Anyone got a clue?
The X keyboard is configured using XKB, which appears to have next to
no documentation, though Google has some more promising links now than
the last time I looked. The XkbRules, XkbModel and XkbLayout options
in XF86Config-4 refer to files in /etc/X11/xkb/ or
/usr/X11R6/lib/X11/xkb/ (which are the same thing on Debian). The
setxkbmap command can change these settings at runtime.
For quick hacks, xmodmap is still supported for compatibility, and can
be easier to use initially.
--
"Hanging is too good for a man who makes puns; he should be drawn and quoted."
-- Fred Allen
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
