I feel like I should understand this, but I don't.
This is x86 assembler. (Actually, looking at the register names, it's probably x86_64. On old school x86, they were named something like al, ah (8 bit), ax (16 bit), or eax (32 bit).) Back in the old days, when you pressed a key on the keyboard, the keyboard controller would generate a hardware interrupt, which, unless masked, would immediately make the CPU jump to a registered interrupt handler, interrupting whatever else it was doing at the point. That interrupt handler would then usually save all registers on the stack, communicate with the keyboard controller to figure out what exactly happened, react to that, restore the old registers again and then jump back to where the CPU was before.
In modern times, USB keyboards are periodically actively polled instead.
The virgin USB: hey, uh, when you get a chance, uh, if it's not too much trouble, could you, uh, put an 'e' there? Whenever you get the chance is fine
The chad PS/2: THE USER SAID E.
I had to write a mini os and it handled keyboard interrupts. Certainly made it make a lot more since after writing it for my uni course
Thanks for the explanation. Ironically this was the bit I didn't know:
In modern times, USB keyboards are periodically actively polled instead.
I was thinking the implication was that some computer had faulty interrupt handling that would smash the status register or something.
Honestly I think I'm just too old to understand memes.
The small bird is a CPU executing its instructions. The big bird is a keyboard sending an interrupt for the CPU to process immediately.
Think of it like breaking news for your processor
"WE INTERRUPT THE CURRENTLY RUNNING APPLICATION TO BRING YOU THIS MESSAGE: e"
And their interrupt routine has an error that leads to changed memory and you don’t know why your Programm calculates „2+6=E“ and that only sometimes on every other run.
REISUB
!!! I just learned about this recently because my PC has an Nvidia GPU and it sometimes wakes up from sleeping to a blank screen with just the mouse cursor showing.
I try that REISUB first but if that doesn't do anything, I have to go to Ctrl-Alt-F3 and do "sudo reboot".
Linux is fun except for when it's not.
You probably have to enable it in sysctl
I once kept opening new terminal sessions then launching a fresh X session while doing something that had a tendency to crash X. I ended up with about 3 crashed graphical sessions by the time I finished what I was doing and actually rebooted!
Hah! This might be the best use of this meme template I've seen. And this template has a lot of good ones.
PS/2 ports?
I'm still mad they killed PS/2 on recent motherboards. So much for NKRO I guess.
Never mind recent motherboards, I'm still salty about the era of boards from 2004-2010 or so which had USB ports but the BIOS would refuse to accept inputs from them until after POST so you'd have to dredge up a separate PS/2 keyboard and jack it in to be able to configure the damn thing or use the boot menu.
And I had at least one board from that time period which has this same flaw, but with the added layer of joy and excitement that they've removed the PS/2 port block in order to appear "modern." It's still there, of course, but only as a pin header that you need to access from inside the case and plug a breakout board into. If you lose that board the gods themselves couldn't even help you. I used to keep it stuck with painters tape to the inside of the case side panel.
Don't forget the xt/at port
someone should have stolen this meme for my intro computer architecture course it would have helped
MOV AX! RB da X!
