https://elinux.org/index.php?title=Thread:Talk:Linux_Drivers_Device_Tree_Guide/Ideas_for_guide_content/reply&feed=atom&action=historyThread:Talk:Linux Drivers Device Tree Guide/Ideas for guide content/reply - Revision history2024-03-28T20:14:41ZRevision history for this page on the wikiMediaWiki 1.31.0https://elinux.org/index.php?title=Thread:Talk:Linux_Drivers_Device_Tree_Guide/Ideas_for_guide_content/reply&diff=380176&oldid=prevFrowand: Reply to Ideas for guide content2015-05-12T21:18:35Z<p>Reply to <a href="/Thread:Talk:Linux_Drivers_Device_Tree_Guide/Ideas_for_guide_content" title="Thread:Talk:Linux Drivers Device Tree Guide/Ideas for guide content">Ideas for guide content</a></p>
<p><b>New page</b></p><div>Additions:<br />
* Accessing DT info<br />
* Tools<br />
** many, many more:<br />
** diff<br />
** config from .dtc<br />
** create overlay from diff<br />
** decompile (already in dtc compiler)<br />
** grep<br />
** utils from the dtc (compiler) git repository<br />
*** fdtdump<br />
*** fdtget<br />
*** fdtput<br />
* How to make a driver more debug-able<br />
* glossary / definitions<br />
* device creation and driver binding ordering dependencies<br />
* Future work in the pipeline (current state, direction, etc)<br />
** overlays<br />
** schema validation<br />
** static boot ordering to reduce delays due to dependencies</div>Frowand