-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oni v2 #68
Conversation
- Reorganized controller into separate pages - Introduce procedures for variable word alignments in high-bw streams - Modified register access to allow queued transactions - Introduce the possibility of optional features - Added an expanded address map
Draft for version 2 of the ONI spec
Split devices page into folder
Redundant since it is on its own file.
- Special devices was duplicated - Device descriptor was duplicated
Remove duplicate text
- Change hub conter name - Split write and read frames
Rewrite channel access concurrency description
- An actual rebase was too difficult, so I brought those branches over manually
Clarify text for hub clocks
Issues 1 and 3
Update device sample definitions
- Reference the formal concept of a network topology and note that ONI hardware is arranged in a tiered star similar to USB
Reference network topology on hierarchy page
- Add glossary term for registers - Specify cotroller and device registers con channel types page
Clarify the meaning of the Trigger register
Reword device channel list
Clarify register description
Improve register maps and hub info
- Looked over the spec as a complete document and created issues for things I felt unsure about - Some formatting changes and minor textual changes for grammer, clarity, etc
OK, Ive completed my review of this. I'm ready to merge this into main, and then merge in the version selection stuff. After this we can default the site to 1.0 and use the normal PR into main mechanism. The build is failing because due to some dependency issue. I did add a new package called |
For now, this is a placeholder for us to track progress. It is also to connect the issues that are being actively worked on, so that it is easier to know what needs to be done next. All issues listed below were found by comparing all of the PRs that were merged from their respective issue-branch into
oni-v2
. Many of them were already closed, but a couple issues were missed.New issues being worked on
Issues from issue branches merged into
oni-v2