[RFC] Abort early or abort late on failure?

[Carl-Daniel Hailfinger]

Hi,

flashrom currently doesn't have a coherent policy about failed writes.
Some chip drivers abort on the first failed write, others keep going
until the end. Either variant makes sense, but mixing them is suboptimal.

The following policies are available:
- hardcode abort early (on first error)
- hardcode abort never (ignore all errors until the end)
- switch behaviour based on commandline parameter.

Opinions?

Regards,
Carl-Daniel

[Maciej Pijanka]

On Wed, 25 Nov 2009, Carl-Daniel Hailfinger wrote:
> Hi,
>
> flashrom currently doesn't have a coherent policy about failed writes.
> Some chip drivers abort on the first failed write, others keep going
> until the end. Either variant makes sense, but mixing them is suboptimal.
>
> The following policies are available:
> hardcode abort early (on first error)
> hardcode abort never (ignore all errors until the end)
> switch behaviour based on commandline parameter.

Imo last option is most sensible, and default might be depend on programming
device used, for internal probably uses stops on first error but may be forced
to postpone error handling until end of operation for external programmers
might by default postpone until end of operation.

Best Regards
Maciej