??? 08/11/06 21:25 Read: times |
#122101 - Definitely not standard Responding to: ???'s previous message |
I noticed that the keyboard would send a make code, then a break code and basically the last byte sent from the keyboard was always 0xE0, not what I expected based on reading various web resources.
Yeah that would cause problems in some places. I have made some that work on PC's and terminals and it's a lot of work to make them all happy -- even if you don't support every last feature. You still have to give the correct response if the host queries for it. A properly published spec would have made life much easier. |
Topic | Author | Date |
PS2 keyboard controller with 8051 | 01/01/70 00:00 | |
Philips appnote | 01/01/70 00:00 | |
Try Google ... lots of help there ... | 01/01/70 00:00 | |
Search here | 01/01/70 00:00 | |
he wants it the other way round | 01/01/70 00:00 | |
The protocol works as described | 01/01/70 00:00 | |
theory vs. reality | 01/01/70 00:00 | |
The Keyboard side. | 01/01/70 00:00 | |
What problems specifaically are you having? | 01/01/70 00:00 | |
It's quite well-defined! | 01/01/70 00:00 | |
Loosely defined | 01/01/70 00:00 | |
re: loosely defined | 01/01/70 00:00 | |
Definitely not standard![]() | 01/01/70 00:00 |