Searched refs:iteration (Results 1 – 10 of 10) sorted by relevance
| /u-boot/lib/ |
| A D | gunzip.c | 93 void gzwrite_progress(int iteration, in gzwrite_progress() argument
97 if (0 == (iteration & 3)) in gzwrite_progress()
134 int iteration = 0; in gzwrite() local
244 gzwrite_progress(iteration++, in gzwrite()
|
| /u-boot/include/ |
| A D | gzip.h | 59 void gzwrite_progress(int iteration, ulong bytes_written, ulong total_bytes);
|
| /u-boot/cmd/ |
| A D | mem.c | 1005 vu_long pattern, int iteration) in mem_test_quick() argument
1016 if (iteration & 1) { in mem_test_quick()
1078 int iteration; in do_mem_mtest() local
1109 for (iteration = 0; in do_mem_mtest()
1110 !iteration_limit || iteration < iteration_limit; in do_mem_mtest()
1111 iteration++) { in do_mem_mtest()
1117 printf("Iteration: %6d\r", iteration + 1); in do_mem_mtest()
1129 iteration); in do_mem_mtest()
1138 printf("\nTested %d iteration(s) with %lu errors.\n", iteration, count); in do_mem_mtest()
|
| /u-boot/doc/develop/ |
| A D | bootstd.rst | 479 of the iteration process, which involves hunting for bootdevs and looking
510 - Otherwise, none of the above flags is set and iteration is set up to work
533 first. Once all have been used, these bootmeths are dropped from the iteration.
548 iteration.
554 The `bootflow_scan_next()` function handles moving onto the next iteration and
581 table on that bootdev, `max_part` can be updated during the iteration to a
590 Assuming that they are entries 3 and 4 in the list, the iteration then looks
618 There is no expectation that iteration will actually finish. Quite often a
637 The above describes the iteration process at a high level. It is basically a
639 checks the result of each iteration generated, to determine whether it can
[all …]
|
| A D | tests_sandbox.rst | 155 iteration, so the `-c` argument to U-Boot is useful.
|
| A D | tests_writing.rst | 191 - test-driven development relies on quick iteration of build/test
|
| /u-boot/doc/usage/cmd/ |
| A D | mtest.rst | 56 Tested 16 iteration(s) with 0 errors.
|
| /u-boot/doc/ |
| A D | README.POST | 352 will allow to detect system rebooting on the previous iteration. For
460 iteration r0/r1 will be used as operands and r2 for result. On
461 the second iteration, r1/r2 will be used as operands and r3 as
669 marked with the POST_REBOOT bit flag. On the first iteration, the
672 the test fails. If the system reboots, on the second iteration the
|
| /u-boot/scripts/ |
| A D | spelling.txt | 863 itertation||iteration
|
| /u-boot/doc/arch/sandbox/ |
| A D | sandbox.rst | 21 rather than needing to test each iteration on real hardware. Many U-Boot
|
Completed in 23 milliseconds