rvf: Fix user defined frame rate constant - #50
Open
edersondisouza wants to merge 1 commit into
Open
edersondisouza wants to merge 1 commit into
edersondisouza wants to merge 1 commit into
Conversation
There's a typo on the 2016 version of IEEE 1722, fixed on 2025 one. Table 42 shows that last value of the octet is the user defined one, so 0xFF (or FF16, depending on notation). But it's written as F16, which is in conflict with the range from 4 to F16 stated as reserved previously. This patch changes the constant to 0xFF. Fixes Avnu#49 Signed-off-by: Ederson de Souza <ederson.desouza@intel.com>
edersondisouza
force-pushed
the
fix-rvf-user-frame-rate
branch
from
September 15, 2026 17:54
a814a25 to
e036fa0
Compare
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
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.
There's a typo on the 2016 version of IEEE 1722, fixed on 2025 one. Table 42 shows that last value of the octet is the user defined one, so 0xFF (or FF16, depending on notation). But it's written as F16, which is in conflict with the range from 4 to F16 stated as reserved previously. This patch changes the constant to 0xFF.
Fixes #49