←back to thread

518 points LorenDB | 2 comments | | HN request time: 0s | source
Show context
trollbridge ◴[] No.46173936[source]
Not to disrespect this, but it used to be entirely normal to have a GUI environment on a machine with 2MB of RAM and a 40MB disk.

Or 128K of ram and 400 kb disk for that matter.

replies(10): >>46173975 #>>46174032 #>>46174138 #>>46174272 #>>46174291 #>>46174522 #>>46174810 #>>46174831 #>>46179105 #>>46179554 #
maccard ◴[] No.46174032[source]
A single 1920x1080 framebuffer (which is a low resolution monitor in 2025 IMO) is 2MB. Add any compositing into the mix for multi window displays and it literally doesn’t fit in memory.
replies(8): >>46174159 #>>46174187 #>>46174618 #>>46174766 #>>46176381 #>>46178650 #>>46179683 #>>46182290 #
echoangle ◴[] No.46174159[source]
Do you really need the framebuffer in RAM? Wouldn't that be entirely in the GPU RAM?
replies(6): >>46174217 #>>46174228 #>>46174232 #>>46174790 #>>46174992 #>>46175002 #
jerrythegerbil ◴[] No.46174232[source]
To put it in GPU RAM, you need GPU drivers.

For example, NVIDIA GPU drivers are typically around 800M-1.5G.

That math actually goes wildly in the opposite direction for an optimization argument.

replies(3): >>46174310 #>>46174452 #>>46175997 #
jsheard ◴[] No.46174452[source]
Doesn't the UEFI firmware map a GPU framebuffer into the main address space "for free" so you can easily poke raw pixels over the bus? Then again the UEFI FB is only single-buffered, so if you rely on that in lieu of full-fat GPU drivers then you'd probably want to layer some CPU framebuffers on top anyway.
replies(2): >>46174701 #>>46174783 #
1. the8472 ◴[] No.46174701[source]
well, if you poke framebuffer pixels directly you might as well do scanline racing.
replies(1): >>46174815 #
2. jsheard ◴[] No.46174815[source]
Alas, I don't think UEFI exposes vblank/hblank interrupts so you'd just have to YOLO the timing.