Lines Matching refs:Binman
16 Binman aims to provide a mechanism for building images, from simple
23 Binman reads your board's device tree and finds a node which describes the
39 Binman can update the device tree with the final location of everything when it
43 Binman can also support incorporating filesystems in the image if required.
46 Binman is intended for use with U-Boot but is designed to be general enough
87 Binman uses the following terms:
105 Binman considers FIT to be one of the binaries it can place in the image.
130 Binman considers the output files created by mkimage to be binary blobs
131 which it can place in an image. Binman does not replace the mkimage tool or
142 Binman aims to replace some of the ad-hoc image creation in the U-Boot
156 Binman is intended to replace the last step. The U-Boot build system builds
157 u-boot.bin and sunxi-spl.bin. Binman can then take over creation of
176 Binman is intended to replace all of this, with ifdtool left to handle only
194 Binman assumes that the input files for the build are in ../b/<board_name>.
208 Binman has a few other options which you can see by running 'binman -h'.
638 Binman normally operates silently unless there is an error, in which case it
700 functions must return True when they have read the contents. Binman will
760 Binman will search for the following files in arch/<arch>/dts:
781 Binman assembles images and determines where each entry is placed in the image.
786 Binman allows you to declare symbols in the SPL image which are filled in
808 A small technical note: Binman automatically adds the base address of the image
826 Binman can update the U-Boot FDT to include the final position and size of
844 Binman support compression for 'blob' entries (those of type 'blob' and
909 Binman can make use of external command-line tools to handle processing of
925 Binman is a critical tool and is designed to be very testable. Entry
936 Binman tries to run tests concurrently. This means that the tests make use of
958 Binman's tests have been written under the assumption that they'll be run on a
1017 Binman takes a lot of inspiration from a Chrome OS tool called