Skip to content

[Wayland] Add support for tearing-control-v1 protocol - #19209

Closed
Sunderland93 wants to merge 11 commits into
libretro:masterfrom
Sunderland93:wayland_tearing
Closed

[Wayland] Add support for tearing-control-v1 protocol#19209
Sunderland93 wants to merge 11 commits into
libretro:masterfrom
Sunderland93:wayland_tearing

Conversation

@Sunderland93

Copy link
Copy Markdown
Contributor

Guidelines

  1. Rebase before opening a pull request
  2. If you are sending several unrelated fixes or features, use a branch and a separate pull request for each
  3. If possible try squashing everything in a single commit. This is particularly beneficial in the case of feature merges since it allows easy bisecting when a problem arises
  4. RetroArch codebase follows C89 coding rules for portability across many old platforms check using C89_BUILD=1

Description

This protocol sends hint to the compositor to allow async page flips via DRM_MODE_PAGE_FLIP_ASYNC. It's tied to Vsync state so when Vsync is off - RetroArch will send async hint and compositor will guarantee that tearing is allowed and non blocked. The protocol allows tearing both for fullscreen and non-fullscreen surfaces, but I don't know if is any of compositors allowing tearing for non-fullscreen surfaces. Tested in KDE Plasma 6.3.5.

Related Issues

[Any issues this pull request may be addressing]

Related Pull Requests

[Any other PRs from related repositories that might be needed for this pull request to work]

Reviewers

[If possible @mention all the people that should review your pull request]

This protocol sends hint to the compositor to allow async page flips. It's tied to
Vsync state so when Vsync is off - RetroArch will send async hint and compositor
will guarantee that tearing is allowed and non blocked. The protocol allows tearing both
for fullscreen and non-fullscreen surfaces, but I don't know if is any of compositors
allowing tearing for non-fullscreen surfaces. Tested in KDE Plasma 6.3.5.
@hizzlekizzle

Copy link
Copy Markdown
Collaborator

This is to allow fast-forwarding instead of forcing sync all the time?

@Sunderland93

Copy link
Copy Markdown
Contributor Author

This is to allow fast-forwarding instead of forcing sync all the time?

Yes

@Sunderland93 Sunderland93 closed this by deleting the head repository Jul 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants