On Fri, Jul 25, 2003 at 07:30:04PM +0900, Norman Diamond wrote:
> > setkeycodes 0x6a 124 1>&2 in your rc.local, local.start or whatever.
> > works fine for me for alle 2.5x kernels
>
> There must be a ton of odd stuff going on. "showkey" used to say that the
> scan code is 0x7d not 0x6a, but now it displays weird stuff. As previously
> mentioned, "getkeycodes" displays a table which seems far removed from
> reality. But the patch from junkio@cox.net worked (but "showkey" and
> "getkeycodes" still produce weird output).
Yes.
I am a little bit unhappy with the state of the kbd code
(but have not yet decided whether I want to attempt to fix something).
One aspect of the matter is that raw mode no longer is raw.
The keyboard sends codes and the input layer translates that into
the codes the input layer thinks the keyboard should have sent.
Then, when one wants the raw codes, a reverse translation is used,
but since the mapping is not one-to-one the reverse translation
does not produce what the keyboard sent to start with.
In particular this means that showkey is no longer useful under 2.5
if one wants to investigate the scancodes a keyboard sends.
Andries
[PS - Some ioctls are broken. Recompiling kernel and loadkeys/dumpkeys
with larger structures works for private use, but the kernel ABI must
not change, so for actual kernel patches one needs new ioctl numbers.]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jul 31 2003 - 22:00:26 EST