Lines Matching refs:Boot

8 For example, we may have SPL, U-Boot, a device tree and an environment area
12 So far U-Boot has not provided a way to handle creating such images in a
14 concatenating images in the U-Boot build system.
17 SPL + U-Boot combinations, to more complex arrangements with many parts.
37 to U-Boot at run-time so that the images can be interpreted.
47 Binman is intended for use with U-Boot but is designed to be general enough
57 devices but is not built in the U-Boot tree. If a Linux kernel is included
60 It is of course possible to add more and more build rules to the U-Boot
78 - Avoids cluttering the U-Boot build system with image-building code
79 - The image description is automatically available at run-time in U-Boot,
97 FIT is U-Boot's official image format. It supports multiple binaries with
103 Now that U-Boot supports configuration via device tree, it is possible to
104 load U-Boot from a FIT, with the device tree chosen by SPL.
114 For U-Boot, binman should not be used to create ad-hoc images in place of
129 called from the U-Boot build system for this reason.
140 Example use of binman in U-Boot
143 Binman aims to replace some of the ad-hoc image creation in the U-Boot
151 2. It uses mkimage to package U-Boot into a legacy image file (so that it can
157 Binman is intended to replace the last step. The U-Boot build system builds
162 This simplifies the U-Boot Makefile somewhat, since various pieces of logic
189 configuring U-Boot (e.g. for sandbox_defconfig the board name is 'sandbox').
196 where <build_path> is the build directory containing the output of the U-Boot
248 normal U-Boot Makefile), some 0xff padding, and a U-Boot legacy image. The
250 CONFIG_SPL_PAD_TO. If that line were omitted then the U-Boot binary would
432 is an example image with two copies of U-Boot. One is read-only (ro), intended
556 10. WriteSymbols() - write the value of symbols into the U-Boot SPL binary.
569 approach supported by the U-Boot build system is to automatically include
571 specific to U-Boot, such as u-boot,dm-pre-reloc properies) in that header
582 U-Boot will only use the first one that it finds. If you need to include a
596 This information may be useful to U-Boot at run time. For example, in SPL it
597 is useful to be able to find the location of U-Boot so that it can be executed
605 declares a ulong value which will be assigned to the offset of any U-Boot
611 Thus u_boot_offset will be set to the offset of U-Boot in memory, assuming that
613 that address to start U-Boot.
616 to fill in such symbols in U-Boot proper, as well.
622 Binman can update the U-Boot FDT to include the final position and size of
627 the device tree. These can be used by U-Boot at run-time to find the location