2024-11-10 14:24:19 -06:00
|
|
|
# Unified PS/2 Driver
|
|
|
|
|
|
|
|
|
|
Te entire thing is heavily documented with comments because I'm not sure how else to make this understandable.
|
|
|
|
|
|
|
|
|
|
## !!Assumptions!!
|
|
|
|
|
Anyone who works on this should work to keep this list as small as possible/remove as many of these as possible.
|
|
|
|
|
- Bit 5 of the response form 0x64 indicates which port the data is coming from. (Not true on all systems)
|
|
|
|
|
- A parity or timeout error never occurs.
|
|
|
|
|
- PS/2 controller exists.
|
|
|
|
|
- Both PS/2 ports being broken doesn't need handling.
|
|
|
|
|
- One PS/2 port being broken doesn't need special attention.
|
|
|
|
|
- PS/2 controller doesn't need to perform a self-check.
|
2024-11-17 14:30:58 -06:00
|
|
|
- These DeviceIDs never exist:
|
|
|
|
|
- 0xFFFD
|
|
|
|
|
- 0xFFFE
|
|
|
|
|
- 0xFFFF
|
|
|
|
|
- 0x01xx
|
|
|
|
|
- 0x03xx
|
|
|
|
|
- 0x04xx
|
