dtc/Documentation/dtc-paper.tex

35 \newcommand{\dtc}{\texttt{dtc}\xspace}
48   The ``blob'' representing the device tree can be created using \dtc
206 included as part of the \dtc (see \S\ref{sec:dtc}) git tree,
315 \label{sec:dtc}
367   \caption{Example \dtc source}
386 so is tedious.  The ``device tree compiler'', \dtc{}\footnote{\dtc can
394 source, \dtc can convert a device tree between a number of
410 In addition, \dtc can output the tree in one of three different
414   straightforward use of \dtc is to compile from ``source'' to
417   input, this allows \dtc to act as a ``decompiler''.
418 \item assembler source (\texttt{asm}).  \dtc can produce an assembler
425 For maximum applicability, \dtc can both read and write any of the
426 existing revisions of the blob format.  When reading, \dtc takes the
431 an explicit \texttt{name} property.  When \dtc creates such a blob, it
438 The ``source'' format for \dtc is a text description of the device
468 \dtc will automatically create a unique phandle for it.  This approach
473 The \dtc source can also include ``labels'', which are placed on a
489 format, \dtc performs a number of checks on the tree:
491 \item \emph{syntactic structure}:  \dtc checks that node and property
495 \item \emph{semantic structure}: In some cases, \dtc checks that
502 \item \emph{Linux requirements}:  \dtc checks that the device tree
526 \subsection{\dtc features}
529 that \dtc could include to make creating device trees more convenient:
531 \item \emph{better tree checking}: Although \dtc already performs a
533   many cases \dtc will give up after detecting a minor error early and
535   \texttt{-f} parameter that forces \dtc to generate an output tree
537   often than one might hope, because \dtc is bad at deciding which
542   incorporate bytecode drivers for certain platform devices.  \dtc's
545 \item \emph{macros}: it might be useful for \dtc to implement some
550   \dtc.  It's not clear whether ``native'' support for macros would be
555 \bibliography{dtc-paper}