Home
last modified time | relevance | path

Searched refs:verbose (Results 1 – 8 of 8) sorted by relevance

/trusted-firmware-a-3.4.0/tools/sptool/
Dspactions.py79 def run_actions(sp_layout: dict, args: dict, verbose=False): argument
95 if verbose:
/trusted-firmware-a-3.4.0/lib/zlib/
Dzutil.c117 # ifndef verbose
118 # define verbose 0 macro
120 int ZLIB_INTERNAL z_verbose = verbose;
/trusted-firmware-a-3.4.0/tools/fiptool/
Dfiptool.c55 static int verbose; variable
468 if (verbose) { in info_cmd()
488 if (verbose) { in info_cmd()
562 if (verbose) in pack_images()
567 if (verbose) in pack_images()
614 if (verbose) { in update_fip()
622 if (verbose) in update_fip()
1001 if (verbose) in unpack_cmd()
1128 if (verbose) in remove_cmd()
1241 verbose = 1; in main()
/trusted-firmware-a-3.4.0/docs/getting_started/
Dtools-build.rst132 verbose. The following command should be used to obtain help about the tool:
152 verbose. The following command should be used to obtain help about the tool:
Dbuild-options.rst1050 To compile a debug version and make the build more verbose use
/trusted-firmware-a-3.4.0/docs/plat/
Drcar-gen3.rst201 order to verbose the BL2 output you will have to compile TF-A with
/trusted-firmware-a-3.4.0/docs/threat_model/
Dthreat_model.rst521 | | very verbose to no output at all. See |
523 | | builds are a lot less verbose than debug ones |
/trusted-firmware-a-3.4.0/docs/
Dchange-log.md901 …- update the log message to verbose ([1277af9](https://review.trustedfirmware.org/plugins/gitiles/…
1124 …- correct verbose message ([47065ff](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trust…
2626 - Do not print duplicate verbose lines about building fiptool
4158 - Building on Windows with verbose mode (`V=1`) enabled is broken
4838 `PLAT_LOG_LEVEL_ASSERT`, which controls how verbose the assert output is.