mirror of
https://github.com/memtest86plus/memtest86plus.git
synced 2025-02-25 18:55:23 -06:00
1eb65bd8bd
Calling clear_screen_region to erase the screen section and then immediately calling printf/prints to write the new information is sub-optimal as the screen gets updated twice. This is especially expensive when Frame Buffer is used. This also creates an unpleasant flickering effect with quickly changing information, like test patterns. Introduce printf_region and prints_region macros to call printf / prints and then clear_screen_region to clear only the region outside the printed area. For consistency, also convert all display_cpu_topo_* macros. Next, avoid redundant screen clearing in display_start_test: - display_test_number already takes care of padding, - test description gets updated immediately after, no need to clear that region. Finally, simplify the code by adding SCREEN_MAX_COL to define the maximum column of the screen, so it can be used instead of SCREEN_WIDTH - 1. |
||
|---|---|---|
| .. | ||
| loongarch | ||
| badram.c | ||
| badram.h | ||
| config.c | ||
| config.h | ||
| display.c | ||
| display.h | ||
| error.c | ||
| error.h | ||
| interrupt.c | ||
| interrupt.h | ||
| main.c | ||
| test.h | ||
| version.h | ||