oxidecomputer / oxidecomputer/hubris
`net` may not need to wait for the sequencer on Cosmo
Open
Nobody has claimed this yet.
cosmo
netstack
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
On Cosmo, net waits for jefe to have a state assigned by cosmo_seq. This may not be necessary!
The comment refers to a clock generator that isn't present on Cosmo; we're using crystals for everything.
Contributor guide
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 with task/net/src/bsp/cosmo_a.rs at lines 56-59 and trace why net waits for jefe to receive a state from cosmo_seq. Compare that wait and its clock-generator comment with the Cosmo hardware described in the issue. Done means determining whether the wait is required and updating the behavior and explanation accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100