From vojtech@suse.cz Thu Apr 6 23:08:40 2000
> > Simply not true. Most likely your i8042 is still switched into AT->XT
> > translating mode and is mangling the Set 3 into unusable garbage. You
> > can see the elegance of Set 3 only after you switch it to direct mode.
>
> You are mistaken. Please check your facts before replying.
>
> [I gave the facts in
> http://www.win.tue.nl/~aeb/linux/kbd/scancodes-3.html#ss3.2
> In case anything there is wrong, please give detailed corrections.
> My statements are true for the keyboards I have here.]
Event: time 955054886.999621, type 1 (Key), code 100 (RightAlt), value 1
Event: time 955054887.121646, type 1 (Key), code 45 (X), value 1
Event: time 955054887.182110, type 1 (Key), code 100 (RightAlt), value 0
Event: time 955054887.194796, type 1 (Key), code 45 (X), value 0
It *works*. In case you'd like to see a full (commented) log of bytes
sent to and from the i8042, I can provide that as well.
I think I know where your problem stems from. You have to explicitely
*enable* break codes in Set 3 by issuing the ATKBD_CMD_SETALL_MB (0xf8)
command.
Yes, precisely. What I describe is the default situation, but indeed,
one can either on a key-by-key basis or for all keys at once
enable or disable key repeat and the production of break codes.
(But again: this only works on certain systems, while scancode set 2
works everywhere; I agree immediately that set 3 is much more elegant,
and that it is a pity that nobody uses it, but now that the code for
set 2 is required anyway, and works everywhere, I cannot see any
advantage in also having the code for set 3. And in the end precisely
the same keycodes must be produced, otherwise one's keymap would depend
on keyboard settings.)
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Apr 07 2000 - 21:00:17 EST