Trading fbdev for DRM, No Returns Accepted
summary
Conversion of legacy fbdev drivers to DRM is feasible but costly: about 100 fbdev drivers remain, an Atari driver is runnable in an emulator using Aranym and modetest after adding new packed and 1bpp formats and endian fixes, patches are queued for v6.1, and many DRM helpers had to be adapted. Performance and memory regressions are real — shadow framebuffers force large RAM use and increase kernel size — Aranym emulator conversion proof +300KB kernel, 10x slower console.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:58Deprecation of Linux Frame Buffer Device Drivers
- 1:40Linux Genesis
- 2:28Linux Expansion
- 4:31Simple Graphics Hardware
- 10:55Fast Graphical Text Consoles
- 13:12Graphics Stack
- 15:18Direct Rendering Infrastructure (DRI/DRM)
- 16:48Kernel Mode Setting (DRM/KMS)
- 24:46Converting Fbdev Drivers to DRM Drivers
- 32:13Analog Displays
- 36:38Performance
- 37:50Example: 1 Mpixel e-Ink Display
- 39:12Conclusion
- 40:05Questions & Answers
related talks
46mGraphic Testing Without Hardware: Discovering the Power of VKMS!
51mAnatomy of an Embedded KMS Driver
52mGetting pixels on screen on Linux: introduction to Kernel Mode Setting
39mOverview of a Modern DRM Driver- 39mOverview of a Modern DRM Driver
44mA Current Overview of the DRM KMS Driver-Side APIs
37mIntegrating Hardware-accelerated Video Decoding with the Display Stack
27mStandardizing Linux DRM drivers implementations by interfacing DRM Bridge as a single...