diff options
| author | Alexander Koch <[email protected]> | 2026-06-12 00:48:34 +0200 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2026-06-29 15:29:44 -0600 |
| commit | a51f24ac31fbb910afc66824e8299a417b297536 (patch) | |
| tree | 41e2abb0ae88d5b3ef140a5c92f926105239b1e7 /src/apps/http/makefsdata | |
| parent | 1537ec5ceb7d80edaefb55743bb44e17f303285b (diff) | |
env: Avoid mixing of environment and driver prints on env load
The current environment loading code prints a partial string
"Loading Environment from %s..." and then triggers env driver
loading function. That env driver loading function may trigger
further prints, either from the env driver itself or from any
other driver that gets probed at that time. The result is a
print which mixed environment loading code prints and driver
code prints, as follows:
"
Environment code print _________________________
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv vv
Loading Environment from SPIFlash... SF: Detected w25q128jw... OK
^^^^^^^^^^^^^^^^^^^^^^
Driver code print
"
Adjust the environment loading code print such, that it places
CR at the end of the line. This way, when the driver code prints
something, it overwrites the previous "Loading Environment from %s"
output and the result is not mixed. Furthermore, in case the env
was loaded correctly, print the "Loading Environment from %s ... OK"
in full again. This either overwrites the "Loading Environment from"
message and appends the print with "OK", or, it prints the line in
full after all the driver code prints.
This is not ideal, but it is the best we can do with only CR and
without ANSI control sequences. The result looks as follows:
"
SF: Detected w25q128jw with page size 256 Bytes, erase size 4 KiB, total 16 MiB
Loading Environment from SPIFlash... OK
"
Signed-off-by: Alexander Koch <[email protected]>
Signed-off-by: Marek Vasut <[email protected]>
Diffstat (limited to 'src/apps/http/makefsdata')
0 files changed, 0 insertions, 0 deletions
