rust-osdev / rust-osdev/uart_16550
Split Config into HwConfig and RtConfig
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 46
- Forks
- 29
- Avg merge
- 10h 48m
- Merged PRs (30d)
- 1
Description
Since we have a new option in #66 , it might make sense to have a config object that differentiates between actual HW properties and just runtime behavioral configs.
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 reading the existing Config definition and the new option introduced in issue #66. Identify which settings represent hardware properties versus runtime behavior, then determine the affected callers and verify that the split into HwConfig and RtConfig preserves the driver's configuration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100