Native gfx init
The wiki is being retired!
Documentation is now handled by the same processes we use for code: Add something to the Documentation/ directory in the coreboot repo, and it will be rendered to https://doc.coreboot.org/. Contributions welcome!
Native graphics init
Is a driver, which is written in a high level language and open source implementation to initialize the graphics hardware on a platform. It might implement only a subset of possible resolution, a subset of possible color depth and work only on a subset of available connectors.
Even though coreboot can run VGA Option ROMs, those aren't called native graphics init.
- NGI : native graphics initialization
- GFX init : graphics initialization
- VBT: Video Bios Tables (Intel specific)
Usage in coreboot
Usually the full color depth and native screen resolution is used. If (x86) VGA hardware is present, one can not assume that it has been initialized at all. A payload should either initialize the GPU on its own or use coreboot tables to gather information about the current state. The payload can not determine if the information provided in coreboot tables is still valid. A bootloader might have changed the GPUs current state.
Libgfxinit in coreboot
libgfxinit is a graphics initialization (aka modesetting) library for embedded environments. It currently supports only Intel hardware, more specifically the Intel Core processor line.
It can query and set up most kinds of displays based on their EDID information. You can, however, also specify particular mode lines.
libgfxinit is written in SPARK, an Ada subset with formal verifica- tion aspects. Absence of runtime errors can be proved automatically with SPARK GPL 2016.
Note: You have to compile the coreboot toolchain with ADA support to use libgfxinit !
"C" native graphics init on pre haswell platforms
On some pre Haswell Intel platforms the graphics can be initialized using C code, but only on the internal LVDS connector.
- VGA Option ROMs contain data BLOBs, that are not available if native graphics initialization is used. OS that rely on those BLOBs won't work as expected.
Note: For some platforms this can be worked around. See VBT for more information.
- No resolution switching at runtime (affects Windows installer)
- No code execution at runtime
- No code BLOBs
- Faster - As code isn't running in real mode
- Debugging output