oxidecomputer / oxidecomputer/hubtools
Factor out Oxide image handling from here and Hubris into a common no_std library
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 5
- Avg merge
- 49m
- Merged PRs (30d)
- 1
Description
Hubtools and Hubris have overlap in their implementations of Hubris/Bootleby image handling that
should be combined into a no_std crate so that there is one source of truth.
This may be limited to the read-only image handling which would be used here and in:
hubris: drv/lpc55-update-server/src/image.rs
hubris: lib/rot-startup/src/image.rs
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 comparing the image-handling implementations in hubris/drv/lpc55-update-server/src/image.rs and hubris/lib/rot-startup/src/image.rs with the corresponding Hubtools code. Identify the overlapping read-only behavior that can move into a no_std crate. Done means both projects use the shared implementation as their single source of truth.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100