Eraseblocks torture: OneNAND results

[Enrico Migliore]

>> FYI: now I see that the tortured eraseblocks do not contain all 0xFFs
>> after erase which is strange - the driver must have returned an error.
>> But mtd->erase is totally silent about this. Most probably it is a bug
>> in the OneNAND driver.
>>
>> May you please take a look at onenand_wait() from
>> drivers/mtd/onenand/onenand_base.c in mtd-2.6.git. I see the following
>> code there:
>>
>>     
Hi,

my name is Enrico, I'm new to this list and I've been reading the 
messages since the end of November.

I've recently read  the Micron's "TN-29-16 Boot from NAND..."  technical 
note and got puzzled by the following:

"Avoid excessive reads to the area of the NAND Flash where code is 
stored. When
repeated accesses are required, the code should be copied to the DRAM. 
This minimizes
the probability of read-disturb errors in the NAND Flash device."

Does that mean that excessive readings might compromise the integrity of 
NAND cells?

Enrico