zlacker

[parent] [thread] 14 comments
1. echoan+(OP)[view] [source] 2025-12-06 15:40:33
Do you really need the framebuffer in RAM? Wouldn't that be entirely in the GPU RAM?
replies(5): >>znpy+W >>sigwin+71 >>jerryt+b1 >>maccar+rd >>Errone+Bd
2. znpy+W[view] [source] 2025-12-06 15:47:55
>>echoan+(OP)
Aren’t you cheating by having additional ram dedicated for gpu use exclusively? :)
3. sigwin+71[view] [source] 2025-12-06 15:50:04
>>echoan+(OP)
VGA standard supports up to 256k
4. jerryt+b1[view] [source] 2025-12-06 15:51:07
>>echoan+(OP)
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+r2 >>jshear+J4 >>hinkle+Et
◧◩
5. Rohans+r2[view] [source] [discussion] 2025-12-06 16:01:01
>>jerryt+b1
> 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+T3
◧◩◪
6. monoca+T3[view] [source] [discussion] 2025-12-06 16:10:59
>>Rohans+r2
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+1c
◧◩
7. jshear+J4[view] [source] [discussion] 2025-12-06 16:17:35
>>jerryt+b1
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+K8 >>throwa+4a
◧◩◪
8. the847+K8[view] [source] [discussion] 2025-12-06 16:48:11
>>jshear+J4
well, if you poke framebuffer pixels directly you might as well do scanline racing.
replies(1): >>jshear+Aa
◧◩◪
9. throwa+4a[view] [source] [discussion] 2025-12-06 17:01:11
>>jshear+J4
Yes if you have UEFI.
◧◩◪◨
10. jshear+Aa[view] [source] [discussion] 2025-12-06 17:04:52
>>the847+K8
Alas, I don't think UEFI exposes vblank/hblank interrupts so you'd just have to YOLO the timing.
◧◩◪◨
11. jshear+1c[view] [source] [discussion] 2025-12-06 17:15:26
>>monoca+T3
That's 100MB of RISC-V code, believe it or not, despite Nvidias ARM fixation.
12. maccar+rd[view] [source] 2025-12-06 17:28:43
>>echoan+(OP)
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
13. Errone+Bd[view] [source] 2025-12-06 17:29:57
>>echoan+(OP)
Computers didn't used to have GPUs back then when 150kB was a significant amount of graphics memory.
replies(1): >>trollb+gP
◧◩
14. hinkle+Et[view] [source] [discussion] 2025-12-06 19:36:27
>>jerryt+b1
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?
◧◩
15. trollb+gP[view] [source] [discussion] 2025-12-06 22:55:44
>>Errone+Bd
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.

[go to top]