oxidecomputer / oxidecomputer/transceiver-control
Do we want to be able to read software power enable bits?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 9
- Forks
- 0
- Avg merge
- 57m
- Merged PRs (30d)
- 3
Description
I recently cleaned up how the embedded system reports how port power enable is reported to be the state of the actual hardware enable pin (see https://github.com/oxidecomputer/quartz/pull/282 and https://github.com/oxidecomputer/hubris/pull/2009). That hardware enable pin has two conditions that must be true for it to drive high: a module must be present and the software power enable control bit must be set. Right now we do not have visibility into the status of that bit in the existing message types.
If we were to want this it would be a trivial add to the ExtendedStatus type.
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
Locate the ExtendedStatus type and inspect the existing message fields for hardware power reporting. Add visibility for the software power-enable control bit, then verify that the status message exposes both conditions relevant to the hardware enable pin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100