zlacker

[parent] [thread] 24 comments
1. maccar+(OP)[view] [source] 2025-12-06 15:26:34
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(4): >>echoan+32 >>snek_c+s9 >>bobmcn+Qb >>beagle+TB
2. echoan+32[view] [source] 2025-12-06 15:40:33
>>maccar+(OP)
Do you really need the framebuffer in RAM? Wouldn't that be entirely in the GPU RAM?
replies(5): >>znpy+Z2 >>sigwin+a3 >>jerryt+e3 >>maccar+uf >>Errone+Ef
◧◩
3. znpy+Z2[view] [source] [discussion] 2025-12-06 15:47:55
>>echoan+32
Aren’t you cheating by having additional ram dedicated for gpu use exclusively? :)
◧◩
4. sigwin+a3[view] [source] [discussion] 2025-12-06 15:50:04
>>echoan+32
VGA standard supports up to 256k
◧◩
5. jerryt+e3[view] [source] [discussion] 2025-12-06 15:51:07
>>echoan+32
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): >>Rohans+u4 >>jshear+M6 >>hinkle+Hv
◧◩◪
6. Rohans+u4[view] [source] [discussion] 2025-12-06 16:01:01
>>jerryt+e3
> NVIDIA GPU drivers are typically around 800M-1.5G.

They also pack in a lot of game-specific optimizations for whatever reason. Could likely be a lot smaller without those.

replies(1): >>monoca+W5
◧◩◪◨
7. monoca+W5[view] [source] [discussion] 2025-12-06 16:10:59
>>Rohans+u4
Even the open source drivers without those hacks are massive. Each type of card has its own almost 100MB of firmware that runs on the card on Nvidia.
replies(1): >>jshear+4e
◧◩◪
8. jshear+M6[view] [source] [discussion] 2025-12-06 16:17:35
>>jerryt+e3
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): >>the847+Na >>throwa+7c
9. snek_c+s9[view] [source] 2025-12-06 16:38:57
>>maccar+(OP)
I had a 386 PC with 4MB of RAM when I was a kid, and it ran Windows 3.1 with a GUI, but that also had a VGA display at 640x480, and only 16-bit color (4 bits per pixel). So 153,600 bytes for the frame buffer.
replies(1): >>Dwedit+E9
◧◩
10. Dwedit+E9[view] [source] [discussion] 2025-12-06 16:40:15
>>snek_c+s9
640 * 480 / 2 = 150KB for a classic 16-color VGA screen.
◧◩◪◨
11. the847+Na[view] [source] [discussion] 2025-12-06 16:48:11
>>jshear+M6
well, if you poke framebuffer pixels directly you might as well do scanline racing.
replies(1): >>jshear+Dc
12. bobmcn+Qb[view] [source] 2025-12-06 16:58:19
>>maccar+(OP)
It's so much fun working with systems with more pixels than ram though. Manually interleaving interrupts. What joy.
◧◩◪◨
13. throwa+7c[view] [source] [discussion] 2025-12-06 17:01:11
>>jshear+M6
Yes if you have UEFI.
◧◩◪◨⬒
14. jshear+Dc[view] [source] [discussion] 2025-12-06 17:04:52
>>the847+Na
Alas, I don't think UEFI exposes vblank/hblank interrupts so you'd just have to YOLO the timing.
◧◩◪◨⬒
15. jshear+4e[view] [source] [discussion] 2025-12-06 17:15:26
>>monoca+W5
That's 100MB of RISC-V code, believe it or not, despite Nvidias ARM fixation.
◧◩
16. maccar+uf[view] [source] [discussion] 2025-12-06 17:28:43
>>echoan+32
You’re assuming a discrete GPU with separate VRAM, and only supporting hardware accelerated rendering. If you have that you almost certainly have more than 2MB of ram
◧◩
17. Errone+Ef[view] [source] [discussion] 2025-12-06 17:29:57
>>echoan+32
Computers didn't used to have GPUs back then when 150kB was a significant amount of graphics memory.
replies(1): >>trollb+jR
◧◩◪
18. hinkle+Hv[view] [source] [discussion] 2025-12-06 19:36:27
>>jerryt+e3
Someone last winter was asking for help with large docker images and it came about that it was for AI pipelines. The vast majority of the image was Nvidia binaries. That was wild. Horrifying, really. WTF is going on over there?
19. beagle+TB[view] [source] 2025-12-06 20:31:46
>>maccar+(OP)
The Amiga 500 had high res graphics (or high color graphics … but not on the same scanline), multitasking, 15 bit sound (with a lot of work - the hardware had 4 channels of 8 bit DACs but a 6-bit volume, so …)

In 1985, and with 512K of RAM. It was very usable for work.

replies(1): >>mrits+GC
◧◩
20. mrits+GC[view] [source] [discussion] 2025-12-06 20:41:06
>>beagle+TB
a 320x200 6bit color depth wasn't exactly a pleasure to use. I think the games could double the res in certain mode (was it called 13h?)
replies(2): >>krige+2F >>teamon+uM
◧◩◪
21. krige+2F[view] [source] [discussion] 2025-12-06 21:04:32
>>mrits+GC
For OCS/ECS hardware 2bit HiRes - 640x256 or 640x200 depending on region - was default resolution for OS, and you could add interlacing or up color depth to 3 and 4 bit at cost of response lag; starting with OS2.0 the resolution setting was basically limited by chip memory and what your output device could actually display. I got my 1200 to display crisp 1440x550 on my LCD by just sliding screen parameters to max on default display driver.

Games used either 320h or 640h resolutions, 4 bit or fake 5 bit known as HalfBrite, because it was basically 4 bit with the other 16 colors being same but half brightness. The fabled 12-bit HAM mode was also used, even in some games, even for interactive content, but it wasn't too often.

◧◩◪
22. teamon+uM[view] [source] [discussion] 2025-12-06 22:14:32
>>mrits+GC
You might be thinking of DOS mode 13h, which was VGA 320x200, 8 bits per pixel.
replies(2): >>banana+CT >>global+BV
◧◩◪
23. trollb+jR[view] [source] [discussion] 2025-12-06 22:55:44
>>Errone+Ef
The IBM PGC (1984) was a discrete GPU with 320kB of RAM and slightly over 64kB of ROM.

The EGA (1984) and VGA (1987) could conceivably be considered a GPU although not turning complete. EGA had 64, 128, 192, or 256K and VGA 256K.

The 8514/A (1987) was Turing complete although it had 512kB. The Image Adapter/A (1989) was far more powerful, pretty much the first modern GPU as we know them and came with 1MB expandable to 3MB.

◧◩◪◨
24. banana+CT[view] [source] [discussion] 2025-12-06 23:14:09
>>teamon+uM
And 6-bits per colour component.
◧◩◪◨
25. global+BV[view] [source] [discussion] 2025-12-06 23:31:21
>>teamon+uM
i remember playing with mode 13h, writing little graphics programs with my turboc compiler. computers were so magical back then.
[go to top]