Lines Matching refs:in

7 Device Tree Control in U-Boot
12 using CONFIG options in the board config file. This feature aims to
20 It is extensible since it consists of nodes and properties in a nice
25 format, and a library is already available in U-Boot (libfdt) for
29 and embedding it in your U-Boot image. This is useful since it allows
32 the features of each board in the device tree file, and have a single
41 An fdt can be specified in source format as a text file. To read about
47 useful: (access this in the Linux kernel source code)
87 well as fdtget/fdtput for reading and writing properties in a binary file.
93 You may find that the Linux kernel has a suitable file. Look in the
94 kernel source in arch/<arch>/boot/dts.
97 modify to your needs. Look in the board directories for files with a
115 This should include your CPU or SOC's device tree file, placed in
122 If CONFIG_OF_SEPARATE is defined, then it will be built and placed in
144 EXT_DTB=<filename> to 'make', as in:
148 Then U-Boot will copy that file to u-boot.dtb, put it in the .img file
151 If you wish to put the fdt at a different address in memory, you can
155 when only the compiled-in environment is available. Therefore it is not
156 possible to define this variable in the saved SPI/NAND flash
162 To use this, put something like this in your board header file:
168 After board configuration is done, fdt supported u-boot can be build in two ways:
190 available in the platform / drivers. It cannot add new drivers (yet). So
192 you need to define CONFIG_SYS_NS16550 to bring in the NS16550 driver,
194 In very broad terms, the CONFIG options in general control *what* driver
195 files are pulled in, and the fdt controls *how* those files work.