summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorStefan Tauner <stefan.tauner@alumni.tuwien.ac.at>2014-07-13 23:53:40 +0000
committerStefan Tauner <stefan.tauner@alumni.tuwien.ac.at>2014-07-13 23:53:40 +0000
commitb543251953f398f75517d94a197e885b751ab1c6 (patch)
treeb0dee908a0c3173b9197347235dae532b04deceb
parent3ef1f600773f8840bea16af4a1ffa458e186cf4a (diff)
downloadflashrom-b543251953f398f75517d94a197e885b751ab1c6.zip
flashrom-b543251953f398f75517d94a197e885b751ab1c6.tar.gz
Improve messages on failed erases with default verbosity
Without this... Erasing and writing flash chip... ERASE FAILED at 0x00001000! Expected=0xff, Read=0xb4, failed byte count from 0x00000000-0x0000ffff: 0xef09 ERASE FAILED! Reading current flash chip contents... done. <loooooong break while the next eraser and writing is tried> Erase/write done. Verifying flash... VERIFIED. Even if there is not a long temporal pause, it is very confusing for the user to first see a failed erase, followed by a read, a done message and eventually the verification message. This patch inserts "Looking for another erase function." where there is just a silent pause above. Corresponding to flashrom svn r1827. Signed-off-by: Stefan Tauner <stefan.tauner@alumni.tuwien.ac.at> Acked-by: Stefan Tauner <stefan.tauner@alumni.tuwien.ac.at>
-rw-r--r--flashrom.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/flashrom.c b/flashrom.c
index 408c555..4f41bf4 100644
--- a/flashrom.c
+++ b/flashrom.c
@@ -1463,9 +1463,9 @@ int erase_and_write_flash(struct flashctx *flash, uint8_t *oldcontents, uint8_t
for (k = 0; k < NUM_ERASEFUNCTIONS; k++) {
if (k != 0)
- msg_cdbg("Looking for another erase function.\n");
+ msg_cinfo("Looking for another erase function.\n");
if (!usable_erasefunctions) {
- msg_cdbg("No usable erase functions left.\n");
+ msg_cinfo("No usable erase functions left.\n");
break;
}
msg_cdbg("Trying erase function %i... ", k);
OpenPOWER on IntegriCloud