Re: ONFI 4GB and beyond NAND support

[Blair Barnett <bbarnett@nethra.us.com>]

>> It appears a simple fix for the erasesize is to use 0x7 as the mask, but
>> the oobsize is a little more problematic.
>>     
>
> I had similar concerns.
> What we did was to just assume that the OOB size was 128 instead of 224.
> We just don't use and our driver sis not concerned about the other 96 bytes.
>   
>> The code
>> mtd->oobsize = (8 << (extid & 0x01)) * (mtd->writesize >> 9);
>>
>> doesn't really work to create a 224 byte oobsize value, not to mention I
>> don't know where to look to create the ECC structure required.
>>     
> As I said above just assume that the OOB is 128 bytes
>
>   
O.K., thanks for the feedback. I thought the bigger OOB size is there 
for allowing more ECC bytes, since the page size is much bigger than 
before and will require more error correction bytes.

I'll work on an ONFI implementation and get it out to the list in the 
next few weeks.

-blair