OneNAND: Update OOB free table

[Timo Teras]

Hi,

On Fri, Dec 08, 2006 at 12:11:06AM +0000, Kyungmin Park wrote:
> Yes, The OneNAND Spec. says these bytes are manged by internal ecc logic.
> Acutually it means that when we write some data in this area. The ecc logic generates the ecc bytes automatically.
> So even though we write 3 bytes. the OneNAND is written by 5 bytes (3 data bytes, 2 space ecc bytes).
> 
> I think we consider the whole spare area. if we don't use this area. we only have 8 bytes of 64 bytes in spare area.
> If it makes misbehavior of JFFS2, we have alternative method turn off ecc logic when write oob area.

Yes. The original problem was that when we wrote JFFS2 clean marker, the ECC
bytes changed which caused JFFS2 code to think the block unclean
effectively considering all clean and empty blocks as dirty at each boot.

> % original
> 
>  OOB Data: ff ff 85 19 03 ff ff ff ff ff ff 30 ff ff ff ff
> 
> % after patch
> 
>  OOB Data: ff ff 85 19 03 ff ff ff ff ff ff ff ff ff ff ff
> 
> Pleaes test this patch

I suppose this fixes the JFFS2 problem as well. 8 bytes of OOB data in a
page should be enough, but having more free OOB space is always a good thing.

Cheers,
  Timo