content: publish practical zephyr device tree #425
Conversation
|
@lmapii I made some grammar edits. Let me know what you think |
|
|
||
| In contrast to _Kconfig_, the *Devicetree* syntax and its use are a bit more intricate. Therefore, we'll cover *Devicetree* in two articles: In this article, we'll see what a Devicetree is and how we can write our own Devicetree source files. In the next article, we'll look at so-called Devicetree _bindings_, which add semantics to our Devicetree. Be prepared for a fair bit of theory, but as usual, we'll use an example project to follow along. |
There was a problem hiding this comment.
For my own information (no pun intended): Does it really sound weird in English to write "write our own source files"? This also popped up in my Grammarly pass, but I really wanted to say that we create our "own" files that are not part of Zephyr, etc.
There was a problem hiding this comment.
In most cases it is seen as redundant, but I agree in this case it adds enough flavor to warrant staying. Will re-add.
|
|
||
| Personally, I felt the details of the [Devicetree specification](https://www.devicetree.org/specifications/) or [Zephyr's official documentation on _Devicetree_](https://docs.zephyrproject.org/latest/build/dts/index.html) a bit overwhelming, and I could hardly keep all the information in my head when reading straight through it (getting lost following links again), so in this article, I'm choosing a slightly different approach: | ||
|
|
||
| Instead of going into great detail about the _DTS (Devicetree Source) format_, we'll start with a simple project, build it, and dive straight into the input and output files used or generated by the build process. Based on those files, one by one, we'll try and figure out how this whole thing works. Finally, we'll also create our own nodes, but we won't fully specify the file format. | ||
| Instead of going into great detail about the _DTS (Devicetree Source) format_, we'll start with a simple project, build it, and dive straight into the input and output files used or generated by the build process. Based on those files, one by one, we'll try and figure out how this whole thing works. Finally, we'll create our own nodes, but we will need to fully specify the file format. |
There was a problem hiding this comment.
This change is a bit weird: I wanted to say that we do not fully specify the file format in this article. The change suggests otherwise, doesn't it?
There was a problem hiding this comment.
Yeah, that wording is a bit strange now that I look at it again. Will revert.
|
Thanks @bahildebrand! Two minor comments and one fix for a broken link, rest looks good to me. |
Co-authored-by: martin <[email protected]>
|
@gminn @bahildebrand something's off, the article exists twice on the blog |
|
@lmapii on it now, I used |
No description provided.