Fix DetailedTiming for hactive beeing a multiple of 256 #1
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
Parsing a DetailedTiming failed for edids, that had a hactive that is divisible by 256, like 1024 for example. This should now be fixed. For the decision if hactive is 0, we now also take the higher 4 bits into account.
|
I'm assuming that the project is dead because there hasn't been any commit in the last 4 years. Though thanks for this PR as I was experiencing the same issue. <3 |
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.
Parsing a DetailedTiming failed for edids, that had a hactive that is divisible by 256, like 1024 for example. This should now be fixed. For the decision if hactive is 0, we now also take the higher 4 bits into account.