Make OBI specs easier to find #672
Merged
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
Signed-off-by: Mike Thompson <[email protected]>
MikeOpenHWGroup
added
the
Component:Doc
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.
I keep getting two questions about the CV32E40P:
1, What are the memory bus interfaces?
2. Where is the location of the OBI spec.?
Both are clearly answered in the User Manual, but it seems the information is not as easy to find as it might be. This PR puts the OBI reference in the Introduction section, which should make it easy to find. In keeping with the "do not repeat yourself" principle of documentation, the links to the spec from the other chapters that reference it have been removed.
By definition this PR will pass an RTL LE check. 😉
Signed-off-by: Mike Thompson [email protected]