Possibility to share device trees and how various OSes have their different copies
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 300
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
The [Device Tree spec](https://devicetree.org) is quite freeform, not requiring much in terms of naming of nodes and properties, or what properties to have, but very few. However, Linux is where DTs are mainly developed, and then copied over to other projects, such as U-Boot and BSDs.
See e.g. https://gist.github.com/orangecms/b8146e5dc35662cc4caddd2e4d5a90c8 comparing Broadcom arm64 device trees in NetBSD vs Linux.
This shows how the two OSes sometimes use different compat strings, which could be worked around by having all possible strings in the respective driver. Node names are a bit tougher.
Some properties may or may not exist in either OS though, and the respective driver is coupled with it.
Document why this is the case, and if OSes can ever use common device trees, including across versions of the same OS.
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 Device Tree specification and the linked gist comparing Broadcom arm64 trees in NetBSD and Linux. Then compare the roles of Linux, U-Boot, and BSD device trees, including compatibility across OS versions. Done means documenting why the trees diverge and whether common device trees are practical.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100