Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

backend/drm: Allow interlaced modes whose resolution is unique #1

Merged
merged 1 commit into from
Oct 5, 2023

Conversation

njhollinghurst
Copy link
Collaborator

This partially reverts the filtering-out of interlaced modes, but we still remove those whose resolution matches a progressive mode (at least until wlr-randr and arandr can be taught to distinguish them).

Need this for TV Out to work on Pi4 and Pi5.

This partially reverts the filtering-out of interlaced modes, but we
still remove those whose resolution matches a progressive mode (at
least until wlr-randr and arandr can be taught to distinguish them).
Copy link
Contributor

@spl237 spl237 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really don't know enough about this particular area to comment, but I trust you!

@6by9
Copy link

6by9 commented Oct 5, 2023

That'll work for now.

It would be nice to offer all modes explicitly, but not for release.

@spl237
Copy link
Contributor

spl237 commented Oct 5, 2023

I'd suggest this doesn't get merged until the release is out of the way - I don't want to be changing wlroots this weekend...

@njhollinghurst
Copy link
Collaborator Author

Ah, I was hoping to get it in before the release so that TV Out would not stop working.

@spl237
Copy link
Contributor

spl237 commented Oct 5, 2023

Is it a regression over the bullseye release if it isn't in? What is Gordon's position on it?

We're well past the point at which we should be making significant changes to core software; we've already had one break post-freeze caused by pulling in upstream changes to wlroots/wayfire at the last minute, and I'd really prefer to avoid the possibility of another.

Unless this is a) a completely risk-free change and b) fixing a showstopping bug, it really shouldn't be going in post release freeze. It can be pulled in on automatic updates once it has had sufficient testing.

@njhollinghurst
Copy link
Collaborator Author

I suppose the main risks are:

  • an unseen coding error causes segfault in some case I haven't tested (which is most cases), or
  • on a monitor whose EDID has progressive and interlaced modes where an interlaced mode is the default or becomes inadvertently selected, that such a mode will cause some unspecified bad thing to happen.

The workaround is to drop back to X11 (or text console) when using TV Out on a Pi4 or Pi5.

@spl237
Copy link
Contributor

spl237 commented Oct 5, 2023

TV Out on Pi 5 requires soldering, IIRC - it doesn't have the connector on the board, so this is really only relevant for Pi 4 in most use cases?

@njhollinghurst
Copy link
Collaborator Author

Yes, or some older HDMI TVs with 1080i but not 1080p. But I must admit I haven't tested that either.

@spl237 spl237 merged commit 6d3ff29 into igalia-bookworm Oct 5, 2023
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.

3 participants