Lines Matching refs:it

13 make it possible for a single U-Boot binary to support multiple boards,
19 for three reasons. Firstly it is easy to use, being a simple text file.
20 It is extensible since it consists of nodes and properties in a nice
24 compiler checks the text file and converts it to a compact binary
29 and embedding it in your U-Boot image. This is useful since it allows
30 U-Boot to configure itself according to what it finds there. If you have
118 If CONFIG_OF_EMBED is defined, then it will be picked up and built into
122 If CONFIG_OF_SEPARATE is defined, then it will be built and placed in
135 it and passes it to U-Boot.
137 If CONFIG_OF_HOSTFILE is defined, then it will be read from a file on
148 Then U-Boot will copy that file to u-boot.dtb, put it in the .img file
155 when only the compiled-in environment is available. Therefore it is not
157 environment, for example (it will be ignored). After relocation, this
179 type. So for example it is not possible to build a single ARM binary