4 ms·
x86 is very dense. Traditional RISCs like MIPS and SPARC are not. ARM is somewhere between the two. Imagine avoiding VGA and instead attempting to support init
by userbinator 7y ago
x86 is very dense. Traditional RISCs like MIPS and SPARC are not. ARM is somewhere between the two.
Imagine avoiding VGA and instead attempting to support initializing a modern graphics card all the way through!
If you just need a framebuffer, and not any kind of acceleration (which is sufficient for something like this), then VBE is a good "better than VGA" (i.e. "SuperVGA") standard you could use. I believe most OSs can fall back to VBE in the absence of GPU-specific drivers.
https://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Other_commonly_available_graphics_modes https://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Other_com...
- Speaking of compatibility, one must wonder how many new layers have been introduced on top of things like VGA since the original VGA.
AFAIK a VGA is basically a framebuffer with a timing controller and some very basic fixed-function hardware to assist the CPU with changing pixel values. A modern GPU, as its name implies, is a complete processor (or more precisely, a massively parallel array of them) that has its own instruction set and runs its own firmware. I believe the basic VGA hardware (i.e. the timing controller, sequencer, DACs, etc.) still exists in somewhat extended form on a modern GPU.
- jchw 7y agoThe true spirit of my thought experiment was, initializing a graphics card, like an NVIDIA card for example, from scratch; sure, VBE works, but no graphics driver actually implements the framebuffer this way. Not saying bothering to do acceleration, just avoiding compatibility layers.
- mjg59 7y agoVBE basically went away with UEFI[1], but on the plus side UEFI basically gives you a function pointer to do mode setup. You just need to jump through multiple other function pointers to find it, which makes everything more annoying... (of course, if you're using UEFI you're also not writing a 512 byte boot sector, so the comparison isn't entirely fair) One meaningful distinction between VBE and the UEFI GOP standard is that you can do VBE calls at OS runtime but can't call GOP after the OS has transitioned away from the boot environment, so modern OSs pretty much require native graphics modesetting for anything other than the case where you only ever need one mode and don't support suspend/resume. [1] OK not strictly true - older UEFI systems would leave a VGA BIOS in the legacy location and let you call it anyway, and UEFI Windows<8 actually relied on this - Windows 8 was the first that would boot on legacy-free UEFI