Lines Matching +full:device +full:- +full:tree
2 ------------------------
15 others. U-Boot is typically found on embedded PowerPC hardware, but there
25 U-Boot (for versions that don't understand the device
26 tree). This image embeds a device tree blob inside
27 the image. The boot wrapper, kernel and device tree
28 are all embedded inside the U-Boot uImage file format
30 bd_info structure and loads the data into the device
31 tree before jumping into the kernel.
33 bd_info structure used in the old U-Boot interfaces,
35 U-Boot platform has a different platform init file
36 which populates the embedded device tree with data
42 dtbImage.%: Similar to zImage, except device tree blob is embedded
47 interface for passing a device tree directly.
59 a device tree blob. This image is a flat binary that
63 the embedded device tree for all information.
78 simpleImage.virtex405-* targets will add the
79 virtex405-head.S initialization code (This also means
81 named (virtex405-<board>.dts). Search the wrapper
83 arch/powerpc/boot/virtex405-head.S for details.
85 on some ppc4xx hardware. This image embeds a device
86 tree blob inside the image.
87 uImage: Native image format used by U-Boot. The uImage target
90 requires a version of U-Boot that is able to pass
91 a device tree to the kernel at boot. If using an older
92 version of U-Boot, then you need to use a cuImage
94 zImage.%: Image format which does not embed a device tree.
96 which are able to supply a device tree. This image
97 expects firmware to provide the device tree at boot.
101 Image types which embed a device tree blob (simpleImage, dtbImage, treeImage,
102 and cuImage) all generate the device tree blob from a file in the
103 arch/powerpc/boot/dts/ directory. The Makefile selects the correct device
104 tree source based on the name of the target. Therefore, if the kernel is
105 built with 'make treeImage.walnut simpleImage.virtex405-ml403', then the
107 treeImage.walnut and arch/powerpc/boot/dts/virtex405-ml403.dts to build
108 the simpleImage.virtex405-ml403.
113 (arch/powerpc/boot/Makefile) by adding targets to the $image-y variable. Look
117 ---------------
134 uses the -p (platform) argument as the main method of deciding which wrapper