mtd-utils: ubiformat: writing images on flash with badblocks.

[Ricard Wanderlof]

On Mon, 12 Sep 2011, Artem Bityutskiy wrote:

>>> when ubiformat encounters a write error while flashing the UBI image (which may
>>> come from a file of from stdout), it correctly marks the faulty eraseblock as
>>> bad and skips it. However, it also incorrectly drops the data buffer which was
>>> supposed to be written, and reads next block of data.
>>
>> I'm just curious, how come this has gone unnoticed for so long? One would
>> think that someone would have tried to flash an image to a chip with bad
>> blocks a long time ago?
>
> No, bad blocks are handled fine. This is about the situation when an
> eraseblock is good, then we write to it, and we get an error, then we
> torture it, and the test fails, and we (ubiformat) mark it as bad. This
> is very rare situation indeed.

Agreed. Sorry I missed the complete background.

/Ricard
-- 
Ricard Wolf Wanderlöf                           ricardw(at)axis.com
Axis Communications AB, Lund, Sweden            www.axis.com
Phone +46 46 272 2016                           Fax +46 46 13 61 30