[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: X server on NetBSD/shark 4.0: protocol wskbd, legacy driver
-----BEGIN PGP SIGNED MESSAGE-----
On Jan 20, 2008, at 14:16, Ignatios Souvatzis wrote:
C2. Much worse: sometimes key release events get lost. It's mostly
harmless when text keys are affected, because pressing it again
will stop the auto-repeat, but I've had the caps lock or even some
sort of control or meta key event (couldn't find out) block in a
way that prevented me from using the keyboard at all in a controlled
I *think* this works fine now that I added
option "protocol" "wskbd"
to the keyboard input section.
I think I know what's wrong - our PS/2 keyboard driver identifies
itself as an XT keyboard but in event mode ( reading from /dev/
wskbd* ) it translates AT extended scancodes ( that's more or less
every key that's present on an AT keyboard but not an XT one ) to not-
really-standard single byte codes which the kbd driver in X ignores
because it expects XT codes and maybe AT multibyte codes. So what I
need to do is to add another translation table to said driver to deal
with those codes. Hopefully that will make those keys work. Doing the
same thing for Xorg will be trivial.
Talk about an ancient bug.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
-----END PGP SIGNATURE-----
Main Index |
Thread Index |