Login
You're viewing the front-end.social public feed.
  • alcinnzalcinnz@floss.social
    May 15, 2026, 9:00 PM

    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/?

    💬 1🔄 0⭐ 0

Replies

  • alcinnzalcinnz@floss.social
    May 15, 2026, 9:15 PM

    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!

    💬 0🔄 0⭐ 0