Lines Matching full:blob
48 The ``blob'' representing the device tree can be created using \dtc
51 the kernel. The compiler can produce either a binary ``blob'' or an
114 compact, flattened format. The resulting device tree ``blob'' is then
116 its runtime form. This blob is the only data communicated between the
122 device tree blob must be passed in from outside, rather than generated
124 \texttt{kexec} tools build the blob from the runtime device tree
125 before invoking the new kernel. For embedded systems the blob can
137 move the blob around as a whole, without needing to parse or adjust
139 within the blob.
144 practice this means limiting the use of internal offsets in the blob
152 \subsection{Format of the device tree blob}
199 \caption{Device tree blob layout}
200 \label{fig:blob-layout}
203 The format for the blob we devised, was first described on the
209 Figure \ref{fig:blob-layout} shows the layout of the blob of data
212 \emph{strings block}. A small header gives the blob's size and
240 of the blob. The name offset is followed by the length of the
248 blob, what actually goes into the tree? The short answer is ``the
309 respectively. To save space in the blob, the current version of the
379 it's usually possible to build the device tree blob at compile time
385 it's possible to hand construct the necessary blob by hand, but doing
389 into the necessary blob.
393 As well as the normal mode of compiling a device tree blob from text
400 \item blob (\texttt{dtb}), the flattened tree format described in
402 device tree blob.
406 for building a blob for the device tree in use by the currently
413 \item blob (\texttt{dtb}), as in \S\ref{sec:format}. The most
415 ``blob'' format.
416 \item source (\texttt{dts}), as in \S\ref{sec:dts}. If used with blob
420 device tree blob, with symbols giving the beginning of the blob and
426 existing revisions of the blob format. When reading, \dtc takes the
427 version from the blob header, and when writing it takes a command line
431 an explicit \texttt{name} property. When \dtc creates such a blob, it
441 gives address ranges to add to the output blob's memory reserve table,
478 addressing the part of the blob with the node or property in question.
483 blob to update the parameter with the correct value determined at
509 the blob input mode, it can also be used for diagnosing problems with
510 an existing blob.
