JFFS2 NAND support - Mount failure on "good" filesystem

[Joshua Wise]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 08 February 2004 3:58 am, Thomas Gleixner wrote:
> Seems like you managed to corrupt the OOB area, as all your blocks are
> marked as bad. Your programming algorithm has to take care of the OOB data
> ! There are some slightly outdated docs on linux-mtd.infradead.org
My programming algorithm is exactly the same as nandwrite's. I believe that 
the issue is not in JFFS2, but in the NAND driver - do we not need multiple 
pages of OOB data, and does the NAND driver not expect the chip to 
automatically "move on"? My chip seems to be the only NAND chip that does not 
automagically move on to the next page of OOB data...

jwise

- -- 
Joshua Wise | www.joshuawise.com
GPG Key     | 0xEA80E0B3
Quote       | <RockShox> charge up a 50v 1000uf cap and toss it to someone
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAJpBBPn9tWOqA4LMRAmZFAJ99i7XLldo46XZaa9txIZOixwzlkACglzPI
9tsTGllBx3OpKu3ZYAM0M9g=
=zlHR
-----END PGP SIGNATURE-----