--Signature_Mon__24_Oct_2005_11_23_55_-0400_LFEXdAxz/F9npSYy
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello,

> >> A lot of this stuff gets swallowed by the ws driver before it ever
> >> gets high enough up the stack for anything to see it. I tried
diving
> >> in a long time ago to find the "extra" keys on my microsoft natural
> >> keyboard. I'm afraid that although I verified the USB device was
> >> sending the codes I gave up after a while trying to understand the
> >> wscons stuff well enough to fix the issue.
> >
> > These events will almost certainly end up in XFree but get swallowed
> > there.
>=20
> Nope. It never makes it that far. I've checked. Really. The problem is
> far far lower down in the wscons stuff. Now, perhaps if the codes were
> making it up to XFree, XFree would also swallow them, but they never
> make it far enough for that to happen.

Hmm, I didn't use the MS keyboard ( Sun Type 6 USB instead ) - wskbd
should just forward unknown ( or better - unmapped ) scancodes to
/dev/wskbd*. But I did quite a lot of work in XFree's keyboard-related
drivers so I doubt we're talking about the same thing here. On x86 you'd
almost certainly use the 'keyboard' driver and ttyE0 as input which
doesn't forward unmapped scancodes while on sparc64 I'm using 'kbd' and
/dev/wskbd0 as input which does.=20
You should be able to read raw scancodes ( in event structs ) from
/dev/wskbd*

have fun
Michael

--Signature_Mon__24_Oct_2005_11_23_55_-0400_LFEXdAxz/F9npSYy
Content-Type: application/pgp-signature

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

iQEVAwUBQ1z8j8pnzkX8Yg2nAQLNRgf/QQFDCu+aYMhMf+Aw0mhNMh+IzINGv0vm
RbMYhIOrWa+4cTe5J4c2Snke0uv9T2nOfcjCs6zW4BWyvsEKJOH3GVDgrDv6J9OZ
aXHfrPjGKbGEPf3pJOED4R4wQa9B91sIlo/CJVu5BjivjoKiKFroul7WnvRFJTee
pNh54x+pGBpVLOn+Sqrd/lNLNar7y80rIFPkKQhmkBN5p0guEGWro2aElv4nwoRP
PYAc8EcOo+LICCTJLt0Zt+MAD1Znasiqz0RZPR+bBWNST5hzwYlnuYhCNRMk3zqV
PtIu3Hy5GjmCp1K2hbgNNi+M3d5Ql90jz5jUmc3KWa7sOwDw+lI3sQ==
=ZVR3
-----END PGP SIGNATURE-----

--Signature_Mon__24_Oct_2005_11_23_55_-0400_LFEXdAxz/F9npSYy--