Skip to content
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

Draft
wants to merge 50 commits into
base: main
Choose a base branch
from
Draft

Oni v2 #68

wants to merge 50 commits into from

Conversation

bparks13
Copy link
Member

@bparks13 bparks13 commented Jan 13, 2025

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

aacuevas and others added 30 commits November 8, 2024 14:31
- 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
- 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
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
aacuevas and others added 16 commits November 21, 2024 17:32
- Add and note to clarify the precise meaning of the Trigger register
  within the device register programming interface on the controller.
Update frame definition and acquisition counter definition
- Name controller registers
- Name hub info device registers
- specift gub info device address map
- add hub datasheet requirement
- clarify optional controller features
- Add glossary term for registers
- Specify cotroller and device registers con channel types page
Clarify the meaning of the Trigger register
Clarify register description
Improve register maps and hub info
@bparks13 bparks13 linked an issue Jan 13, 2025 that may be closed by this pull request
@bparks13 bparks13 added this to the 2.0 milestone Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment