Lines Matching full:image

7 PowerPC image targets compresses and wraps the kernel image (vmlinux) with
10 be adaptable for each kind of image that needs to be built.
13 Makefile in that directory has targets for all the available image types.
14 The different image types are used to support all of the various firmware
19 firmware interface requires a different image format.
23 image.  The details of the build system is discussed in the next section.
24 Currently, the following image format targets exist:
29 			tree).  This image embeds a device tree blob inside
30 			the image.  The boot wrapper, kernel and device tree
48 			inside the image instead of provided by firmware.  The
49 			output image file can be either an elf file or a flat
65    simpleImage.%:	Firmware independent compressed image that does not
67 			a device tree blob.  This image is a flat binary that
70 			kernel with this image type and it depends entirely on
73    treeImage.%;		Image format for used with OpenBIOS firmware found
74 			on some ppc4xx hardware.  This image embeds a device
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
85    zImage.%:		Image format which does not embed a device tree.
87 			which are able to supply a device tree.  This image
90 			hardware then you want this image format.
93 Image types which embed a device tree blob (simpleImage, dtbImage, treeImage,
103 (arch/powerpc/boot/Makefile) by adding targets to the $image-y variable.  Look
104 at the Makefile to see which default image targets are available.
109 that a single vmlinux image can be booted on many different target boards.
118 The wrapper is adapted for different image types at link time by linking in
119 just the wrapper bits that are appropriate for the image type.  The 'wrapper
121 is responsible for selecting the correct wrapper bits for the image type.