DTB (FDT) parsing & patching, choosing device tree libraries
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.8k
- Forks
- 113
- PR merge metrics
- No merged PRs in 30d
Description
For dtb based platforms, we need the ability to pass memory configuration (DRAM size, notably), which is determined at runtime.
We do have a small library around device trees already for layoutflash, our internal library for the DTFS (device tree file system), currently depending on repnop/fdt.
RustSBI has another library, supporting serde: https://github.com/rustsbi/serde-device-tree
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 with the existing device-tree library dependency in src/lib/layoutflash/Cargo.toml and compare repnop/fdt with rustsbi/serde-device-tree. Determine which library can support patching DTB data for runtime memory configuration, especially DRAM size; the work is done when a library choice and integration path are established.
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
- 20/100