OneNAND: Always print error messages

[Adrian Hunter]

ext Kyungmin Park wrote:
>>>> If a load error occurs when scanning a bad block, does that mean the dataRAM
>>>> has been updated or not?
>>> scanning a bad block means read oob so we don't update dataRAM. In onenand implementation. we always invalid dataRAM in oob case.
>> 
>> I meant the dataRAM spare area: 8010h - 804fh in the bufferRAM address map.
>> 
>> After a load error, will this:
>> 
>> 		this->read_bufferram(mtd, ONENAND_SPARERAM, buf, column, thislen);
>> 
>> read the what was meant to be loaded, or will it still contain the data from a previous load?
> 
> => It depends on load error timings. but we think it is always invalid.
> load error means that there's error during load from nand core to bufferram.

So, when scanning for bad blocks, after a load error or ECC (2 bit) error, we have to
assume that the block is bad without reading the spare area?

In that case, should we attempt to mark the block as bad,
perhaps writing the spare area in the second page?