| ??? 08/04/06 18:07 Read: times |
#121660 - re: loosely defined Responding to: ???'s previous message |
Grant Beattie said:
Once you get down to the nitty gritty of making something that has to boot on every PC out there, you quickly find out that the docs on the web are pretty incomplete. Indeed. I've been playing with a PS/2 keyboard interface (it's in an FPGA, so sorry if it's OT) and 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. Of course, maybe it was the cheap-ass keyboard I bought for $5 at 9:45pm at the local used book/record/crap store (which we love) 'cause my USB ports on my PC decided to not work and I couldn't uninstall a driver without a keyboard. I need to look at what's going on using my logic analyzer ... I need more samples than I get with my 'scope. Anyways, there are a handful of references out there. Computer-engineering.org has pages about the protocol and the interface which are pretty good. -a |
| 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 |