Generating a NAND Image

[Thomas Gleixner]

On Friday 16 May 2003 00:01, Charles Manning wrote:
> The one problem with doing it this way is that you end up with the bad
> blocks in your image file too. THis will be a problem when you go to
> manufacturing because the manufacturing writer needs to skip over bad
> blocks it detects as it writes. Your image will then not fit any more and
> you'd be marking good blocks bad.
True. Did not htink about that.

> Rather, IMHO, - if you're using YAFFS-  suck the structure off the NAND
> onto a host (eg. NFS copy the directory structure to the host) and use
> mkyaffsimage. Send them the myyaffsimage output file.  I guess there's a
> JFFSx process to do the same thing.
There's no OOB generator yet, but that's a good idea for volunteers :)

> Alternatively (useful to both YAFFS and JFFS2)  hack nanddump.c to not
> write bad blocks to the dump file. This will definitely work for YAFFS, but
> I'm not 100% sure it will work for JFFS2.
Sure, why not. JFFS2 does not rely on bad blocks. :)

> ... and submit a patch :-).
:)

-- 
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx at linutronix.de