kms: Output mirroring #448
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Output mirroring! Including cases of mismatched resolutions/orientations/refresh-rates/gpus
TODO:
Optimize happy path, where we can attach the connector to the crtc of the source surface directlyTBD after the larger KMS refactoroutputs.ron)Clear color for letterboxed mirrors?Lets just use blackCan we possibly allocate a dmabuf instead of a texture as a render target for better performance?Not worth it.Would enable us to keep the render-device (faster rendering, but a new copy operation..)Found a way to do this without another copy and without a dmabufPotentially eligible for direct-scanout (though in these cases the dimensions never match up, can any display controller actually handle this?)I don't think they can, not worth the trouble.