Post
GRUB outputs imagery to a screen for you to interact with (assuming that you can see it, which isn't a safe assumption), so there's a whole subsystem for generating & outputting that imagery!
This includes a couple small byte arrays of output for initializing sm712 displays. And a couple for sis315, one of which is non-trivially long.
There's a driver for Radeon Yeeloong3a GPUs. Its info&fini method copies a property over to the caller & invokes generic finalization.
1/?
GRUB's Radeon Yeelong render-target setter invokes a generic implementation with a saved fallback value. It doesn't swap buffers. Its setup method validates config's supported, locates the GPU on the PCI bus (via a callback which retrieves the framebuffer), populates the "mode" properties, registers the memory-mapped I/O, zeroes it out, & calls generic routines to configure the render target.
There's an initializer & finalizer which additionally manages the memory-mapped I/O.
2/?
The Radeon Fuloong2e driver works very similarly.
There's a simple parser for RGB colours which strongly resembles a subset of CSS's, including the same dubious lookup table of named colours.
There's an in-memory driver used by the test suite with a callback invoked upon swapping buffers. Alongside public routines for setting up & tearing down this driver, or retrieving its framebuffer.
There's a bitmap object wrapping image data with structural metadata, & a linkedlist of parsers.
3/3!
Install bonfire.cafe
Get the full app experience
