Lines Matching full:tree
16 An important part of falcon boot is to prepare the device tree. A normal U-Boot
18 SPL, skipping the normal U-Boot. The device tree has to be prepared in advance.
20 It is equivalent to go through "bootm" step-by-step until device tree fixup is
21 done. The device tree in memory is the one needed for falcon boot. Falcon boot
25 Linux, the device tree stored in FIT image overwrites the memory loaded by spl
29 to understand the device tree in FIT image should be the one actually used, or
31 image with embedded static device tree to multiple boards.
34 the stored sectors to. Normally this is the static device tree. The second
39 is no longer used. The static device tree is copied into this location. So
40 this macro is passed as the location of device tree when booting Linux.
42 Steps to prepare static device tree
44 To prepare the static device tree for Layerscape boards, it is important to
47 microcode (if used) is embedded in the device tree. Kernel command line and
58 stops before "bootm go". There we have the fixed-up device tree in memory.
59 We can check the device tree header by these commands
64 Where the fdt address is the device tree in memory. It is printed by U-Boot.
66 tree is to save it to eMMC/SD using command in U-Boot, and extract under Linux
74 When we have the static device tree image, we can re-make the FIT image with
78 Generate FIT image with static device tree
100 description = "Flattened Device Tree blob";