On 1/26/26 11:14, Christian König wrote: > On 1/23/26 15:44, Timur Kristóf wrote: >> On Friday, January 23, 2026 2:52:44 PM Central European Standard Time >> Christian König wrote: >> >>> So as far as I can see the whole approach doesn't make any sense at all. >> >> Actually this approach was proposed as a solution at XDC 2025 in Harry's >> presentation, "DRM calls driver callback to attempt recovery", see page 9 in >> this slide deck: >> >> https://indico.freedesktop.org/event/10/contributions/431/attachments/ >> 267/355/2025%20XDC%20Hackfest%20Update%20v1.2.pdf >> >> If you disagree with Harry, please make a counter-proposal. > > Well I must have missed that detail otherwise I would have objected. > > But looking at the slide Harry actually pointed out what immediately came to > my mind as well, e.g. that the Compositor needs to issue a full modeset to > re-program the CRTC.
In principle, the kernel driver has all the information it needs to reprogram the HW by itself. Not sure why the compositor would need to be actively involved. -- Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer https://redhat.com \ Libre software enthusiast
