Searched refs:summary (Results 1 – 19 of 19) sorted by relevance
| /rk3399_rockchip-uboot/fs/jffs2/ |
| H A D | jffs2_1pass.c | 1312 struct jffs2_raw_summary *summary, in jffs2_sum_process_sum_data() argument 1320 sp = summary->sum; in jffs2_sum_process_sum_data() 1322 for (i = 0; i < summary->sum_num; i++) { in jffs2_sum_process_sum_data() 1382 struct jffs2_raw_summary *summary, uint32_t sumsize, in jffs2_sum_scan_sumnode() argument 1397 crcnode.totlen = summary->totlen; in jffs2_sum_scan_sumnode() 1400 if (summary->hdr_crc != crc) { in jffs2_sum_scan_sumnode() 1406 if (summary->totlen != sumsize) { in jffs2_sum_scan_sumnode() 1411 crc = crc32_no_comp(0, (uchar *)summary, in jffs2_sum_scan_sumnode() 1414 if (summary->node_crc != crc) { in jffs2_sum_scan_sumnode() 1419 crc = crc32_no_comp(0, (uchar *)summary->sum, in jffs2_sum_scan_sumnode() [all …]
|
| /rk3399_rockchip-uboot/tools/buildman/ |
| H A D | control.py | 228 if not options.summary: 291 Print(GetActionSummary(options.summary, commits, board_selected, 301 if options.summary:
|
| H A D | builder.py | 1190 summary = {} 1254 summary[target] = '\n'.join(lines) 1257 for target, lines in summary.iteritems():
|
| H A D | test.py | 293 options.summary = False
|
| H A D | README | 30 A key feature of buildman is its output summary, which allows warnings, 68 Buildman produces a concise summary of which boards succeeded and failed. 545 To find out how the build went, ask for a summary with -s. You can do this 826 Shown below the summary lines are the sizes for each board. Below each board 990 summary for 'arm' showing all the changes detected for that architecture. 1062 buildman just shows a summary, with red indicating that a commit introduced 1119 -S shows image sizes for each commit (just an overall summary)
|
| /rk3399_rockchip-uboot/doc/ |
| H A D | README.fsl_iim | 29 using "Word y of Bank x" from the register summary in 30.3.2. This is
|
| H A D | README.unaligned-memory-access.txt | 51 here; a summary of the common scenarios is presented below: 188 In summary, the 2 main scenarios where you may run into unaligned access
|
| H A D | README.ti-secure | 200 interface to those functions is shown in the code. The summary
|
| H A D | README.nand | 171 printing a size summary. This should also make it easier to
|
| H A D | README.x86 | 721 Timer summary in microseconds:
|
| /rk3399_rockchip-uboot/board/sbc8349/ |
| H A D | README | 42 is a summary of that information:
|
| /rk3399_rockchip-uboot/doc/uImage.FIT/ |
| H A D | command_syntax_extensions.txt | 16 Below is a summary of bootm usage scenarios, focused on booting a PowerPC
|
| /rk3399_rockchip-uboot/test/py/ |
| H A D | README.md | 74 then print a summary of the test process. A complete log of the test session 140 details. Execute `py.test --version` for a brief summary. Note that U-Boot's
|
| /rk3399_rockchip-uboot/board/hisilicon/poplar/ |
| H A D | README | 74 required by one or the other user). It also includes a summary of
|
| /rk3399_rockchip-uboot/board/sbc8548/ |
| H A D | README | 157 The following contains some summary information on hardware settings
|
| /rk3399_rockchip-uboot/scripts/ |
| H A D | checkpatch.pl | 35 my $summary = 1; 213 'summary!' => \$summary, 6386 if ($summary && !($clean == 1 && $quiet == 1)) {
|
| /rk3399_rockchip-uboot/common/ |
| H A D | Kconfig | 38 Timer summary in microseconds:
|
| H A D | dlmalloc.src | 63 Prints brief summary statistics on stderr. 65 Returns (by copy) a struct containing various summary statistics.
|
| /rk3399_rockchip-uboot/ |
| H A D | README | 65 http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary 4861 Chris Hallinan posted a good summary of these issues to the
|