Lines Matching +full:platform +full:- +full:data

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
28 			are all embedded inside the U-Boot uImage file format
29 			with boot wrapper code that extracts data from the old
30 			bd_info structure and loads the data into the device
33 			bd_info structure used in the old U-Boot interfaces,
34 			cuImages are platform specific.  Each specific
35 			U-Boot platform has a different platform init file
36 			which populates the embedded device tree with data
37 			from the platform specific bd_info file.  The platform
38 			specific cuImage platform init code can be found in
45 			binary depending on the platform.
49 			dtbImages have platform specific code for extracting
50 			data from the board firmware, but simpleImages do not
55 			file named arch/powerpc/boot/<platform>.c; but this
61 			Firmware cannot pass any configuration data to the
67 			the Xilinx Virtex platform).  The only assumption that
71 			  simpleImage also supports inserting special platform
73 			sequence.  The virtex405 platform uses this feature to
75 			is enabled.  Platform specific initialization code is
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.
87    uImage:		Native image format used by U-Boot.  The uImage target
89 			vmlinux in the uImage data structure.  This image
90 			requires a version of U-Boot that is able to pass
92 			version of U-Boot, then you need to use a cuImage
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
135 bits to compile in.  Look for the large 'case "$platform" in' block in the
136 middle of the script.  This is also the place where platform specific fixups