[sai-gen] Parse P4 metadata into SAI spec for lib generation. #576
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
|
Hi @marian-pritsak check out the ca to pa spec! : D with this info, we should be able to fix the field id problem for good! |
r12f
changed the title
r12f
changed the title
r12f
changed the title
r12f
changed the title
r12f
changed the title
marian-pritsak
approved these changes
Jun 18, 2024
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.
The current SAI spec has all the information for header generation. To simplify the lib generation as well, parse the SAI to P4 info mapping into SAI spec too.
This can simplify the SAI lib templates, as we don't have to do too many checks in the templates anymore.