tree fe01f2dc6954114e565a0a5eaad30b54a29d21db
parent 7427569e2572cc8182e056876c0c67ddae213fc3
author Nico Huber <nico.h@gmx.de> 1730799019 +0100
committer Nico Huber <nico.h@gmx.de> 1730891742 +0000

Drop 1s delay before automatic verification

This delay was added in commit 8ab49e72af84 (Disallow erase/write for
known bad chips so people won't try without a clear understanding) to
help with "a few reports where verify directly after erase had unplea-
sant side effects".

Since 2011 however,  commit b4061f61cdf9  (Move erase verification to
generic code),  we read each erased block back directly,  without any
delay.  So it seems the original problem is either gone, or would hit
us much earlier.

Grepping through 3 years of mailing-list archives, also didn't reveal
anything specific.  Most reports of failed verifications could be ex-
plained with write protections. More recent ones were about SPI flash
chips with auto address increment (AAI) writes, where flashrom didn't
erase automatically before writing  (and hence gave rather suspicious
results).

Change-Id: I9871ee7085156816bfffb117cda60b9267990609
Signed-off-by: Nico Huber <nico.h@gmx.de>
Reviewed-on: https://review.sourcearcade.org/c/flashprog/+/269
Reviewed-by: Angel Pons <th3fanbus@gmail.com>