build: unify verbosity handlingThis change introduces a few helper variables for dealing with verboseand silent build modes: `silent`, `verbose`, `q` and `s`.The `silent` and `verbose` variables
build: unify verbosity handlingThis change introduces a few helper variables for dealing with verboseand silent build modes: `silent`, `verbose`, `q` and `s`.The `silent` and `verbose` variables are boolean values determiningwhether the build system has been configured to run silently orverbosely respectively (i.e. with `--silent` or `V=1`).These two modes cannot be used together - if `silent` is truthy then`verbose` is always falsy. As such: make --silent V=1... results in a silent build.In addition to these boolean variables, we also introduce two newvariables - `s` and `q` - for use in rule recipes to conditionallysuppress the output of commands.When building silently, `s` expands to a value which disables thecommand that follows, and `q` expands to a value which supppressesechoing of the command: $(s)echo 'This command is neither echoed nor executed' $(q)echo 'This command is executed but not echoed'When building verbosely, `s` expands to a value which disables thecommand that follows, and `q` expands to nothing: $(s)echo 'This command is neither echoed nor executed' $(q)echo 'This command is executed and echoed'In all other cases, both `s` and `q` expand to a value which suppressesechoing of the command that follows: $(s)echo 'This command is executed but not echoed' $(q)echo 'This command is executed but not echoed'The `s` variable is predominantly useful for `echo` commands, where youalways want to suppress echoing of the command itself, whilst `q` ismore useful for all other commands.Change-Id: I8d8ff6ed714d3cb401946c52955887ed7dca602bSigned-off-by: Chris Kay <chris.kay@arm.com>
show more ...
refactor(fiptool): move plat_fiptool.mk to toolsMove all plat_fiptool.mks into tools, change the logic to recursivelycheck for tools/fiptool/plat_fiptool/<plat_path>/plat_fiptool.mkI.e. for a pl
refactor(fiptool): move plat_fiptool.mk to toolsMove all plat_fiptool.mks into tools, change the logic to recursivelycheck for tools/fiptool/plat_fiptool/<plat_path>/plat_fiptool.mkI.e. for a platform that has the path "plat/arm/board/tc/platform.mk",the makefile will now load the first existing file from: - tools/fiptool/plat_fiptool/arm/board/tc/plat_fiptool.mk - tools/fiptool/plat_fiptool/arm/board/plat_fiptool.mk - tools/fiptool/plat_fiptool/arm/plat_fiptool.mkThis enables fiptool to support multiple platforms, or a specific one.Remove file-copying previously being used to handle old default path.Remove custom file cleaning in plat_fiptool.mk.Change-Id: I95245bcf7143b329481d4394ab64f29bfe9de5abSigned-off-by: Raef Coles <raef.coles@arm.com>
nxp: fip-handler for additional fip_fuse.binAll of the NXP SoC, needs fip_fuse image to beloaded additionally as part of preparation for Trusted board boot- fip_fuse.bin contains an image for aut
nxp: fip-handler for additional fip_fuse.binAll of the NXP SoC, needs fip_fuse image to beloaded additionally as part of preparation for Trusted board boot- fip_fuse.bin contains an image for auto fuse provisioning.- Auto fuse provisioning is based on the input file with values for: -- SRK Hash -- OTPMK -- misc. refer board manual for more details.Signed-off-by: Pankaj Gupta <pankaj.gupta@nxp.com>Change-Id: I26d4024fefe352d967ca120191f784f1f47aa9d1