Re: X server on NetBSD/shark 4.0: protocol wskbd, legacy driver

[Michael <macallan1888%gmail.com@localhost>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

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
> > way.
>
> 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.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQEVAwUBR5iko8pnzkX8Yg2nAQK97Af/UI0TB3aylppRhoCYinEIXiAM8qhWnQQL
1qis0CL31TxwdsrHaiFX+nsQHgVrMOODqQcenSEFsbcTfvrE3o7dPNKFuv7E7aVi
cMoE2UQNqtq5JvHyIVFPkuKSxohTPnLrtGhtNJ4CplxWHXmpV+ZA6+hNdzHruDnp
Af/FbIDcw12BirlbefSY/OX4+FRCg3XRwxfSukFlhT40OwoTp+fd8htMZVQ1d/TA
2cmqazjvKFxRYu285xSeVEpovJ5PdHRblOPw89AY31pcsYhZu/ts5degnpOtglGi
d8of1Wsz6JGN89O3Ggtea/dfBgiFVwxQ7CCt54wTJ4DB/iw2ihFVhg==
=8scV
-----END PGP SIGNATURE-----