- cross-posted to:
- linux_memes@programming.dev
- cross-posted to:
- linux_memes@programming.dev
You must log in or register to comment.
assembly flashbacks
thanks for that KeyboardInterrupt
PS/2 Port on its way to harass the CPU
Seems the CPU has become the bully these days:
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
Keyboard: E
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
…My grandpa always used to say that computers used to be way better before they became electrical.
Ah, yes the good ol days of punch cards, switch boards, mechanical operators and electron tubes, when will the youngins learn that their fancy transistors are for pussies
Personally I inscribe all of my code into binary on a fired clay tablet and store it in a cave for archival purposes
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.
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.
