[PATCHJ] [MTD] [OneNAND] Allow for controller errors when reading

[Adrian Hunter]

Kyungmin Park wrote:
> On Fri, Apr 11, 2008 at 8:05 PM, Adrian Hunter
> <ext-adrian.hunter at nokia.com> wrote:
>> Controller errors while reading can be caused by
>>  corruption caused by a previous powerloss. Because
>>  upper level software like JFFS2 treat -EIO as fatal,
>>  it is necessary to treat the error as an ECC error.
>>
> 
> Umm interesting. You mean it occurs controller error before ecc error
> at power loss case.
> And it needs to define the terminology the Sudden Power Off Recovery
> or POR shortly.
> I'm not sure a previous powerloss means POR.

No it is not what I meant.  I have sent another patch which I hope is
clearer.

> Anyway could you show the controller error value?

The controller error value is still printed.

> Since it needs to
> distinguish others e.g., initial bad blocks condition.

The bbt scan has its own wait function - I guess it is
possible to get a controller error while reading oob
from an eraseblock that is not actually a bad block.
I am not sure how it would be possible to tell the
difference.