Modern USB keyboards need to be asked what’s being pressed by the CPU multiple times a second, but old PS/2 keyboards will actually interrupt the CPU to send the key press command
It’s kind of a tradition among the r*ddit refugees from s*bs like linuxmemes and linuxmasterrace. Posting things that aren’t strictly linux-related, but would still be appreciated in general by computer nerds.
I don’t get it…
Modern USB keyboards need to be asked what’s being pressed by the CPU multiple times a second, but old PS/2 keyboards will actually interrupt the CPU to send the key press command
Oh, didn’t actually know what’s being done behind the scene…
Why is this relevant to Linux only?
It’s not
Hm… then why is it posted in a Linux comm?
Because it’s funny, there’s nothing that you don’t already know.
It’s kind of a tradition among the r*ddit refugees from s*bs like linuxmemes and linuxmasterrace. Posting things that aren’t strictly linux-related, but would still be appreciated in general by computer nerds.
Ah, didn’t know that 👍.
I see you had interruptions masked.
Why e in this context? I have seen
sei()andcli()before, but notE.That’s the very important information you got from the keyboard.
Some context may come later, but it will take ages.
Thanks, apparently I can’t read. I somehow missed the top right yellow speech bubble.