summaryrefslogtreecommitdiff
path: root/board_enable.c
diff options
context:
space:
mode:
authorstefanct <stefanct@2b7e53f0-3cfb-0310-b3e9-8179ed1497e1>2014-07-13 23:53:40 +0000
committerstefanct <stefanct@2b7e53f0-3cfb-0310-b3e9-8179ed1497e1>2014-07-13 23:53:40 +0000
commit25ad9288c50f4681f9a00b1761dc4105c47f6e9d (patch)
treeb0dee908a0c3173b9197347235dae532b04deceb /board_enable.c
parent2ae5af4999bac7fbf60b93976b4e3e5a4566a560 (diff)
downloadflashrom-25ad9288c50f4681f9a00b1761dc4105c47f6e9d.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. Signed-off-by: Stefan Tauner <stefan.tauner@alumni.tuwien.ac.at> Acked-by: Stefan Tauner <stefan.tauner@alumni.tuwien.ac.at> git-svn-id: https://code.coreboot.org/svn/flashrom/trunk@1827 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1
Diffstat (limited to 'board_enable.c')
0 files changed, 0 insertions, 0 deletions