https://bugs.kde.org/show_bug.cgi?id=514454
--- Comment #2 from [email protected] --- (In reply to Zamundaaa from comment #1) > The reason for this could be that KWin sets HDR metadata each frame. With > legacy modesetting, setting any properties may cause the driver to do a > pageflip, so if we set the property + then another frame, the driver might > end up pushing two frames instead of one. > > There are some workarounds we can consider, like splitting out the code path > for "allow_modeset" in KWin to a separate function, but as no actual legacy > drivers support HDR, maybe the best course of action would be to just remove > the feature from legacy. Looking at drmdb.emersion.fr, the same applies to > VRR as well. > > Why are you using legacy in the first place though? It's "legacy" for a > reason, it's not supposed to be used unless your driver doesn't support the > proper API. I've considered ripping out the env var to force it as well... Hi, many thx for taking a look ! The reason is simple, it is that one : https://gitlab.freedesktop.org/drm/amd/-/issues/2950 Disabling AMS is the only way i am not plagued by crtc timeouts. And i am by far not the only one. So no matter what you plan to do, please do NOT REMOVE the KWIN_DRM_NO_AMS=1 option . I will simply go ahead and disable VRR when i enable HDR in the no ams usecase. Many thx ! Pingubot -- You are receiving this mail because: You are watching all bug changes.
