Lines Matching refs:flattened

44   flattened-tree representation of the system's hardware based on the
55   This flattened-tree approach is now the only supported method of
114 compact, flattened format.  The resulting device tree ``blob'' is then
121 directly from the entry point taking a flattened device tree.  The
129 \subsection{Properties of the flattened tree}
131 The flattened tree format should be easy to handle, both for the
141   make tweaks to the flattened tree, such as deleting or inserting a
143   having to effectively regenerate the whole flattened tree.  In
247 Having seen how to represent the device tree structure as a flattened
249 same as an OF tree''.  On OF systems, the flattened tree is
254 device tree.  The flattened tree need only provide those nodes and
255 properties that the kernel actually requires; the flattened tree
258 PCI device on the system.  A flattened tree need only include nodes
276 One complication arises for representing ``phandles'' in the flattened
290 In the flattened tree, a node's phandle is represented by a special
291 \phandle property.  When the kernel generates a flattened tree from
310 flattened tree format only requires the unit names to be present.
371 As we've seen, the flattened device tree format provides a convenient
374 manipulate.  On OF systems, it's easy to generate the flattened tree
376 flattened tree must be generated from scratch.
400 \item blob (\texttt{dtb}), the flattened tree format described in
516 The flattened device tree has always been the only supported way to
522 to the flattened device tree approach.  We plan to remove the
524 various embedded boards to use the flattened device tree.