Getting the raw state of the keyboard with CauseWay? (Developers)
I made a first move in writing my own keyboard driver. Posted on usenet.
I cannot recommend anyone trying it out on real hardware; not until I understand exactly what the inp() and outp() routines are doing. It also beeps for a long time on first use in DOSBox-X, and I think that's something to do with my code rather than DOSBox-X.
If anyone here has some comments on the code, please share.
Complete thread:
- Getting the raw state of the keyboard with CauseWay? - myrkraverk, 18.10.2019, 00:57 (Developers)
![Open in board view [Board]](img/board_d.gif)
![Open in mix view [Mix]](img/mix_d.gif)
- Getting the raw state of the keyboard with CauseWay? - myrkraverk, 18.10.2019, 01:26
- Getting the raw state of the keyboard with CauseWay? - myrkraverk, 18.10.2019, 19:35
- Getting the raw state of the keyboard with CauseWay? - myrkraverk, 21.10.2019, 12:48
- Getting the raw state of the keyboard with CauseWay? - Japheth, 21.10.2019, 14:58
- Getting the raw state of the keyboard with CauseWay? - myrkraverk, 23.10.2019, 01:16
- Getting the raw state of the keyboard with CauseWay? - Japheth, 21.10.2019, 14:58
- Getting the raw state of the keyboard with CauseWay? - myrkraverk, 21.10.2019, 12:48
- Getting the raw state of the keyboard with CauseWay? - myrkraverk, 18.10.2019, 19:35
- Getting the raw state of the keyboard with CauseWay? - myrkraverk, 18.10.2019, 01:26
Mix view