oxidecomputer / oxidecomputer/humility
humility gpio -i could include config information
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 584
- Forks
- 63
- Avg merge
- 3h
- Merged PRs (30d)
- 2
Description
When looking at the output of humility gpio -i, you see the current state of the GPIO, e.g. 0 or 1, but not whether it is currently configured as an input or output. This changes a bit about how you interpret the state. As an example, the state of a pin at reset is an input it may actually be 0, but that is very different from it outputting a zero.
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 at the humility gpio -i command entry point and trace how it reads and formats the current GPIO state. Determine where the input/output configuration is available, then update the command's output to show that configuration alongside the state; done means reset inputs and driven outputs can be distinguished.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools, embedded-iot
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100