Post Syndicated from jake original https://lwn.net/Articles/955708/

Displaying an application’s graphical output onto the screen requires
compositing and
mode setting that are correctly synchronized among the various pieces,
with low overhead.
In this second and final article in the series, we will look at
those pieces of the Linux graphics stack. In the first installment, we
followed the path of graphics from the application, through Mesa, while
using the
memory-management features of the kernel’s Direct
Rendering Manager (DRM) subsystem.
We ended up with an application’s graphics data stored in an output buffer,
so now
it’s time to display the image to the user.