Lines Matching +full:u +full:- +full:boot

2 The PowerPC boot wrapper
8 a boot wrapper to make it usable by the system firmware. There is no
9 standard PowerPC firmware interface, so the boot wrapper is designed to
12 The boot wrapper can be found in the arch/powerpc/boot/ directory. The
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
22 it uses the wrapper script (arch/powerpc/boot/wrapper) to generate target
28 U-Boot (for versions that don't understand the device
30 the image. The boot wrapper, kernel and device tree
31 are all embedded inside the U-Boot uImage file format
32 with boot wrapper code that extracts data from the old
37 bd_info structure used in the old U-Boot interfaces,
39 U-Boot platform has a different platform init file
43 `arch/powerpc/boot/cuboot.*.c`. Selection of the correct
62 file named arch/powerpc/boot/<platform>.c; but this
77 uImage: Native image format used by U-Boot. The uImage target
78 does not add any boot code. It just wraps a compressed
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
88 expects firmware to provide the device tree at boot.
95 arch/powerpc/boot/dts/ directory. The Makefile selects the correct device
98 arch/powerpc/boot/dts/walnut.dts to build treeImage.walnut.
102 Default images are selected by the boot wrapper Makefile
103 (arch/powerpc/boot/Makefile) by adding targets to the $image-y variable. Look
107 ---------------
110 It also means that the boot wrapper must be able to wrap for many kinds of
112 conditional compilation code (#ifdef, etc) in the boot wrapper source code.
113 All of the boot wrapper pieces are buildable at any time regardless of the
120 script' (found in arch/powerpc/boot/wrapper) is called by the Makefile and
124 uses the -p (platform) argument as the main method of deciding which wrapper