Lines Matching refs:Binman

18 Binman aims to provide a mechanism for building images, from simple
25 Binman reads your board's device tree and finds a node which describes the
41 Binman does not yet update the device tree with the final location of
46 Binman can also support incorporating filesystems in the image if required.
49 Binman is intended for use with U-Boot but is designed to be general enough
90 Binman uses the following terms:
108 Binman considers FIT to be one of the binaries it can place in the image.
133 Binman considers the output files created by mkimage to be binary blobs
134 which it can place in an image. Binman does not replace the mkimage tool or
145 Binman aims to replace some of the ad-hoc image creation in the U-Boot
159 Binman is intended to replace the last step. The U-Boot build system builds
160 u-boot.bin and sunxi-spl.bin. Binman can then take over creation of
179 Binman is intended to replace all of this, with ifdtool left to handle only
192 Binman assumes that the input files for the build are in ../b/<board_name>.
206 Binman has a few other options which you can see by running 'binman -h'.
393 functions must return True when they have read the contents. Binman will
435 Binman will search for the following files in arch/<arch>/dts:
455 Binman is a critical tool and is designed to be very testable. Entry
492 Binman takes a lot of inspiration from a Chrome OS tool called