oxidecomputer / oxidecomputer/hubris
Want a means of getting at current hotplug FPGA state
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
There are some issues that I'm trying to debug where the host seems to think presence is asserted for something that should not be. It's not clear to me right now if this is a Sidecar issue, a cable issue, a Cosmo FPGA issue, or just a classic illumos kernel bug (as my luck usually goes). What would have helped was the ability to read the raw fpga state registers that represent what it thinks it's seeing. That would have helped us bifurcate this a bit.
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 by tracing how hotplug presence state is represented and where the Cosmo FPGA state is accessed. Determine the appropriate entry point for exposing the raw FPGA state registers without assuming whether the issue is in Sidecar, the cable, the FPGA, or illumos. Done means a user can read the relevant raw state needed to distinguish those failure sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100