kms: Don't use more then 10-bit by default #1518
Draft
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Draft because I am not sure this actually fixes anything and will be more annoying to deal with, once we might actually want to scanout XRGB16161616 with HDR content.
But there isn't really any reason this is necessary currently, we never use a format with more than 10-bits, and this might run into bandwidth issues otherwise, which currently require manual edits of
outputs.ron.We possibly want to tie this to the selected format in the future and downgrade step-by-step both the format and requested max_bpc, if we get atomic-commit errors.