Typing with one hand (and not the useful one): not good. On Tue, 16 Sept 2025 at 11:46, Daniel Stone <dan...@fooishbar.org> wrote: > Again though, it's not something new. I promise you that Weston (for > over a year), Mutter (for about a year), KWin (for over two years), > and wlroots (for two and a half years) already have hard deps on > libdisplay-info. Even outside of 'serious' compositors, Mesa requires > it to support HDR in VK_KHR_display (when it was added a couple of > months ago),
... and mpv has also required it for any DRM backend support (same as all the compositors) for the past year. So yeah, I see it as the same as the input situation: you _can_ do the basics with raw evdev, but unless you're very special, you should use libinput. Equally for output, when you go past what e.g. Plymouth would require, use libdisplay-info to parse the EDID, rather than trying to make the kernel try to turn the unhinged madness of EDID into something userspace can reason about. Cheers, Daniel
