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

Hello,

On Dec 5, 2006, at 16:56, Arto Huusko wrote:

>>> And I'm wondering how can I go about using wskbd?
>>> If I set keyboard protocol to wskbd and device to
>>> /dev/wskbd (or /dev/wskbd0), X claims that it can't
>>> open the device (I added errno printing, and the error
>>> is EBUSY, which is not really surprising, given that
>>> the keyboard is attached to console...)
>>
>> Try /dev/wskbd0
>
> Tried both wskbd and wskbd0 and they both fail
> the same way: EBUSY (doesn't the mux claim wskbd0).

Hmm, it works here.

> Am I even right in the assumption that X server needs to
> somehow make the console release the wskbd before it
> opens it? If not, how is X and console supposed to share it?

No, you should be able to just open /dev/wskbd or /dev/wskbd0.
The problem with /dev/wskbd is that when you have two different 
keyboards - like on sun and one USB - then X won't be able to handle 
both correctly since they use different scancodes and X assumes one 
device corresponds to one keyboard.

So, are you actually using a wscons kernel? Does NetBSD's XFree86 work 
correctly?

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

iQEVAwUBRXZIpspnzkX8Yg2nAQJcZAf+LNNMMZD//itr2l4JTMur8mtf5q3z/+Wz
Pa0RN7CbrNoFjTmIlKQMOyFhxFIpNdq83Zj0+N52clDEfN3k2qbkgZsmpIvyqhfo
iicJtGRlo2/NBm1S7q38NrfxVvCaGW2dg3GQvLTeCCFVSCtGYbC4TaSJjeHxXNtt
GXHAkOLFeqvk9DpaxRHw6aB1b8vGLLkj6j6PhQpVVyjpbya83ODYcQYVBJi0vlyY
GTxog2IWCvrvgbY82wW6/5jAf7Kx2Wx1a/96J79OBAYp4VainPl7xTOMbcXxjF8V
OkNRL7eBf1RRHPuilmXXxRLrSmDuhGYlcTptLT4PR9F4dtoISuY0qg==
=Nbu4
-----END PGP SIGNATURE-----