oxidecomputer / oxidecomputer/transceiver-control
Need a design for SP -> Host information flow
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 9
- Forks
- 0
- Avg merge
- 57m
- Merged PRs (30d)
- 3
Description
We don't really have a design for the SP -> Host class of requests yet to my knowledge. We could have the host poll regularly (via a new HostRequest message )and get the updates in bulk, but I'd rather we build out SpRequest messages to indicate presence changes, interrupts from modules, and hardware faults. This also feels like an important thing to solve imminently, so I'd propose we add it to the FCS milestone.
@bnaecker thoughts?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing SpRequest messages and the host-side request handling; the issue does not name specific files or tests. Compare the proposed SpRequest approach with a new HostRequest polling message, then document an agreed design for presence changes, module interrupts, and hardware faults that can be added to the FCS milestone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100