mirror of
https://review.coreboot.org/flashrom.git
synced 2025-09-13 16:51:58 +02:00
Erase should respect --noverify option
This commit adds check for the flag `verify_after_write` after erase operation and does not perfom verification if the flag disabled. From command line, this is set by --noverify option. libflashrom flag is FLASHROM_FLAG_VERIFY_AFTER_WRITE Default stays the same, by default verification is performed. This commit also adds test for the scenario. Previously, erase operation ignored --noverify option and always performed verification. For more details, see Ticket: https://ticket.coreboot.org/issues/520 Change-Id: I9f6cb7210f4dcdc32870f9096657a08b12e77c7f Signed-off-by: Anastasia Klimchuk <aklm@flashrom.org> Reviewed-on: https://review.coreboot.org/c/flashrom/+/88734 Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org> Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Carly Zlabek <carlyzlabek@gmail.com> Reviewed-by: Matt DeVillier <matt.devillier@gmail.com> Reviewed-by: Vincent Fazio <vfazio@gmail.com>
This commit is contained in:
@@ -72,14 +72,14 @@ All operations involving any chip access (probe/read/write/...) require the ``-p
|
||||
|
||||
|
||||
**-n, --noverify**
|
||||
Skip the automatic verification of flash ROM contents after writing. Using this option is **not** recommended,
|
||||
Skip the automatic verification of flash ROM contents after writing or erasing. Using this option is **not** recommended,
|
||||
you should only use it if you know what you are doing and if you feel that the time for verification takes too long.
|
||||
|
||||
Typical usage is::
|
||||
|
||||
flashrom -p prog -n -w <file>
|
||||
|
||||
This option is only useful in combination with ``--write``.
|
||||
This option is only useful in combination with ``--write`` or ``--erase``.
|
||||
|
||||
|
||||
**-N, --noverify-all**
|
||||
|
Reference in New Issue
Block a user