--Signature_Tue__9_Aug_2005_15_16_47_-0400_+WpA6pxyDRRoZNzu
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello,

I've got the following problem: the Apple Extended II keyboard
apparently sends one-byte scancodes with the upper bit indicating wether
the key was pressed or released for all keys, except caps-lock. This one
is always followed by a 0, which translates to an 'a'.=20
Is this normal or is my keyboard hosed?
I don't have any other ADB keyboards to check. The ADB code in NetBSD
apparently deals with this in some way, at least on the console the
caps-lock key doesn't do anything funny, but in X which reads raw
scancodes it produces an extra a or A. So - should I hack the keyboard
handling in X to ignore the 0 after caps-lock? This would be something
hardware-specific in a pretty much abstract driver, or should I just
suppress it in our ADB code?=20
Sun keyboards do something similar - send a 0x7f after each scancode -
but 0x7f isn't used for any key so we just map it to nothing - since 0
/is/ used we can't do that with ADB.

ideas?

have fun
Michael

--Signature_Tue__9_Aug_2005_15_16_47_-0400_+WpA6pxyDRRoZNzu
Content-Type: application/pgp-signature

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

iQEVAwUBQvkBH8pnzkX8Yg2nAQIfQQf7B/kVfvjsjXgxPIcPQ91hduv80FMT7f4R
m/+f3zBI0A6rPGwQS2enVsG6liPs5Zeu7g6t+FTzMuhMN0ZnM/SB7QQMeaUA+yfa
3fY8CWG1xaojgNMIW9lun464b8UarVV+Jm3d/XBUI3WkazoZvDkdXFrJprxdP/QU
QhHMAsuRJ9M++u7YZP6DE2T6VeSiYz6po9HSxflYdyWStm/Qy4VQMm8Gj7CNVCZL
/b+q6ZZ8qvAvk6d/sNIjrsAU07hvvZG2IqVsks46T/hw+lKkVdngXC0fee4//a1S
op4lQcjuGTAyruOiq1W2Dx2HHJnBSN7d6dtk+bLsxJlnorNDBHPs7A==
=AaiE
-----END PGP SIGNATURE-----

--Signature_Tue__9_Aug_2005_15_16_47_-0400_+WpA6pxyDRRoZNzu--