Hi,
If it wasn't for this quote...
ThisIsAnEpicUsername wrote:
This happens sometimes on real hardware, always on QEMU and never in Bochs. Is this an issue with my driver, or with PS/2 keyboard using scan code set 2?
...my question is that you do realize that a break code for set 2 is 0xF0 and then the key that is being released?
For example, when you press 'S', you will get a single byte from the keyboard: 0x1B
When you release the 'S', you will get two bytes from the keyboard: 0xF0 and 0x1B
Are you mistakenly thinking that the 0x1B is a new 'make' code?
However, since you did say the above quote, I agree with Octocontrabass, I think it to be within your driver, and a log is a good suggestion.
Ben
-
https://www.fysnet.net/osdesign_book_series.htm