--Signature_Wed__3_Aug_2005_11_08_57_-0400_vH_AFJSfPf4oN5Hf
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello,

> My qestion is, what's the story with 'Driver "kbd"' and 'Option
> "Protocol" "wskbd"'? I mean is this supposed to be the new driver for
> keybards or does 'X -configure' get is completely wrong?

That's a longer story.
'keyboard' has a bunch of funky design limitations that make it nearly
unusable ( or at least very quirky ) on non-PC-keyboards. Besides that
it's a horrible mess. That's why I initially switched the whole thing to
'kbd' which is much cleaner and works well with Sun- and ADB-keyboards.
Later it turned out that 'kbd' apparently omits some keycode mangling
done by 'keyboard' which is needed to support PS/2 keyboards properly,
so I changed the code again to default to 'kbd' only on sparc64 and
macppc. If you run 'X -configure' with something less than 2 weeks old
you should get 'keyboard' again.=20
I can't really fix the PS/2 stuff right now because I have no NetBSD box
with a PS/2 keyboard. A cleaner solution would probably check the
keyboard type and then write 'keyboard' or 'kbd' instead of just
hardcoding it architecture-dependent.

have fun
Michael

--Signature_Wed__3_Aug_2005_11_08_57_-0400_vH_AFJSfPf4oN5Hf
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (NetBSD)

iQEVAwUBQvDeDspnzkX8Yg2nAQLJggf/cwCWutqG5w6zaOuClDB44/RzdHwOgqIs
oU0g0Lg1pZ9dbitd8BOEXr5lyZn9ng1jYDe0YNQgcFIkkYYdaIoIikpPOFr6W4nb
z6ip63GZIhpFxMgT4g+xnAisz3/tNqbO+P/jgkptEv60BoAX3ltabMwUz3+rsXaS
ETNL+HLplqYFDfxEXA7lVVw1TfrT52Rm34ucw/yX6kLgimdy87jHx99wZyY5HqKC
7Q6bd0GOMa/U8lwhODMdtsRWB2j0M4p6sVIhbSx9uyDUINiTW3F7LT5KCbTxEgjY
gQrMQjzLy/LQSSsuBHUDGumxrYZSfQvgmmIxj3wXpGL9LdUjFrbOZw==
=HKdx
-----END PGP SIGNATURE-----

--Signature_Wed__3_Aug_2005_11_08_57_-0400_vH_AFJSfPf4oN5Hf--