Lines Matching refs:image

5 PowerPC image targets compresses and wraps the kernel image (vmlinux) with
8 be adaptable for each kind of image that needs to be built.
11 Makefile in that directory has targets for all the available image types.
12 The different image types are used to support all of the various firmware
17 firmware interface requires a different image format.
21 image.  The details of the build system is discussed in the next section.
22 Currently, the following image format targets exist:
26 			tree).  This image embeds a device tree blob inside
27 			the image.  The boot wrapper, kernel and device tree
43 			inside the image instead of provided by firmware.  The
44 			output image file can be either an elf file or a flat
57    simpleImage.%:	Firmware independent compressed image that does not
59 			a device tree blob.  This image is a flat binary that
62 			kernel with this image type and it depends entirely on
77 			the image target name.  For example, all
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
89 			vmlinux in the uImage data structure.  This image
96 			which are able to supply a device tree.  This image
99 			hardware then you want this image format.
113 (arch/powerpc/boot/Makefile) by adding targets to the $image-y variable.  Look
114 at the Makefile to see which default image targets are available.
119 that a single vmlinux image can be booted on many different target boards.
128 The wrapper is adapted for different image types at link time by linking in
129 just the wrapper bits that are appropriate for the image type.  The 'wrapper
131 is responsible for selecting the correct wrapper bits for the image type.