Lines Matching +full:platform +full:- +full:data
17 others. U-Boot is typically found on embedded PowerPC hardware, but there
28 U-Boot (for versions that don't understand the device
31 are all embedded inside the U-Boot uImage file format
32 with boot wrapper code that extracts data from the old
33 bd_info structure and loads the data into the device
37 bd_info structure used in the old U-Boot interfaces,
38 cuImages are platform specific. Each specific
39 U-Boot platform has a different platform init file
40 which populates the embedded device tree with data
41 from the platform specific bd_info file. The platform
42 specific cuImage platform init code can be found in
50 binary depending on the platform.
55 dtbImages have platform specific code for extracting
56 data from the board firmware, but simpleImages do not
62 file named arch/powerpc/boot/<platform>.c; but this
69 Firmware cannot pass any configuration data to the
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
82 version of U-Boot, then you need to use a cuImage
103 (arch/powerpc/boot/Makefile) by adding targets to the $image-y variable. Look
107 ---------------
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
126 middle of the script. This is also the place where platform specific fixups