View source for Talk:Linux Drivers Device Tree Guide

Jump to: navigation, search


Thread titleRepliesLast modified
Ideas for guide content114:18, 12 May 2015
outline014:13, 12 May 2015
audience114:08, 12 May 2015

Ideas for guide content

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.


Return to Thread:Talk:Linux Drivers Device Tree Guide/Ideas for guide content.


  • Accessing DT info
  • Tools
    • many, many more:
    • diff
    • config from .dtc
    • create overlay from diff
    • decompile (already in dtc compiler)
    • grep
    • utils from the dtc (compiler) git repository
      • fdtdump
      • fdtget
      • fdtput
  • How to make a driver more debug-able
  • glossary / definitions
  • device creation and driver binding ordering dependencies
  • Future work in the pipeline (current state, direction, etc)
    • overlays
    • schema validation
    • static boot ordering to reduce delays due to dependencies
Frowand (talk)14:18, 12 May 2015
  • Overview
  • Syntax
  • Tools
  • Initialization
  • Conventions
  • Debugging
  • API (to drivers)
  • Resources
14:13, 12 May 2015

The main audience for the guide is Linux device driver developers.

A secondary audience is sub-system maintainers, who want to know more, specifically, about guidelines for bindings.

14:02, 12 May 2015

Additional audience:

Sysadmins (trying to set up or configure a device tree based system).

Distro creators and maintainers.

Frowand (talk)14:08, 12 May 2015