Lines Matching +full:in +full:- +full:tree
12 The boot wrapper can be found in the arch/powerpc/boot/ directory. The
13 Makefile in that directory has targets for all the available image types.
17 others. U-Boot is typically found on embedded PowerPC hardware, but there
21 The boot wrapper is built from the makefile in arch/powerpc/boot/Makefile and
23 image. The details of the build system is discussed in the next section.
28 U-Boot (for versions that don't understand the device
29 tree). This image embeds a device tree blob inside
30 the image. The boot wrapper, kernel and device tree
31 are all embedded inside the U-Boot uImage file format
34 tree before jumping into the kernel.
36 Because of the series of #ifdefs found in the
37 bd_info structure used in the old U-Boot interfaces,
39 U-Boot platform has a different platform init file
40 which populates the embedded device tree with data
42 specific cuImage platform init code can be found in
44 cuImage init code for a specific board can be found in
47 dtbImage.%: Similar to zImage, except device tree blob is embedded
53 interface for passing a device tree directly.
61 specific initialization code is typically found in a
67 a device tree blob. This image is a flat binary that
68 can be loaded to any location in RAM and jumped to.
71 the embedded device tree for all information.
75 tree blob inside the image.
77 uImage: Native image format used by U-Boot. The uImage target
79 vmlinux in the uImage data structure. This image
80 requires a version of U-Boot that is able to pass
81 a device tree to the kernel at boot. If using an older
82 version of U-Boot, then you need to use a cuImage
85 zImage.%: Image format which does not embed a device tree.
87 which are able to supply a device tree. This image
88 expects firmware to provide the device tree at boot.
93 Image types which embed a device tree blob (simpleImage, dtbImage, treeImage,
94 and cuImage) all generate the device tree blob from a file in the
96 tree source based on the name of the target. Therefore, if the kernel is
103 (arch/powerpc/boot/Makefile) by adding targets to the $image-y variable. Look
107 ---------------
112 conditional compilation code (#ifdef, etc) in the boot wrapper source code.
116 tested in a large variety of environments.
118 The wrapper is adapted for different image types at link time by linking in
120 script' (found in arch/powerpc/boot/wrapper) is called by the Makefile and
122 The arguments are well documented in the script's comment block, so they
124 uses the -p (platform) argument as the main method of deciding which wrapper
125 bits to compile in. Look for the large 'case "$platform" in' block in the
129 In particular, care should be taken when working with cuImages. cuImage