Handle "opaque bus" subspaceMap scenario #33
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
This only covers an "opaque bus" scenario ("Memory map in opaque
bridge").
Additionally adds `filter` argument, which can be used to parse only one
memoryMap, instead of all of them. If no filter is provided, all maps
will be put into a top-level addrmap (previously the tool would just put
the last memoryMap parsed into the RDL file).
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.
This only covers an "opaque bus" scenario ("Memory map in opaque bridge") when processing the
subspaceMapelement.Additionally adds
filterargument, which can be used to parse only one memoryMap, instead of all of them. If no filter is provided, all maps will be put into a top-level addrmap with a configurable name (previously the tool would just put the last memoryMap parsed into the RDL file).