Open Source Summit Europe 2022

DRI, DRM, KMS, FB, EGL, Wayland, V4L2: The Linux graphics stack can be very confusing and intimidating. Unfortunately, the first contact is usually when a system is not performing as expected and needs to be debugged. This situation can easily occur for embedded systems with a graphical user interface. Due to hardware resource constraints, handling the large amount of data involved in graphics makes it necessary to use optimized hardware paths to fulfill (soft) real-time system requirements such as a certain frame rate. Understanding these acronyms and the components that constitute the graphics stack is necessary for working with the internals on embedded systems. This is essential for optimizing a system's graphics performance or investigating observed performance issues, and communicating findings to others. To make the Linux graphics stack less scary, Michael will take you by the hand and give you a guided tour. We will find out, which software components are involved in the Linux graphics stack, and discuss which APIs are used to interact with these components and which should be avoided. Furthermore, we will look at the tools and methods which can be used for debugging.