diff options
| author | Simon Ser <contact@emersion.fr> | 2023-06-12 12:13:21 +0200 |
|---|---|---|
| committer | Kenny Levinsen <kl@kl.wtf> | 2023-06-12 20:38:03 +0000 |
| commit | 4339c37f99aa311e300205a7d27c43e470ae93da (patch) | |
| tree | 98cfb853d890683927cba03e0f591d7f8a101686 /examples | |
| parent | a09bb1314de6296545aae5146658ac1259ae6c40 (diff) | |
backend/drm: clip FB damage
The kernel complains when the damage exceeds the FB bounds:
[73850.448326] i915 0000:00:02.0: [drm:drm_atomic_check_only] [PLANE:31:plane 1A] invalid damage clip 0 0 2147483647 2147483647
Make the DRM backend behave like the Wayland one and allow compositors
to damage (0, 0, INT32_MAX, INT32_MAX) to repaint everything without
needing to know the exact buffer size.
Closes: https://github.com/swaywm/sway/issues/7632
Diffstat (limited to 'examples')
0 files changed, 0 insertions, 0 deletions