I have figured out part of the problem, with nanddump the default block size is 4096 but the default spare_data size is 128 not 64 bytes. I am testing my code now for reconstruction and having some success. On Thu, Jun 23, 2011 at 10:41 AM, Peter Pilley wrote: > I was thinking that this morning on my drive in, I am going to play with > the chunk size again and see what I can come up with. > > The default is 2048 correct?. > > > On Thu, Jun 23, 2011 at 9:55 AM, Charles Manning wrote: > >> On Wednesday 22 June 2011 16:32:48 Peter Pilley wrote: >> > Everyone on list. >> > >> > I was doing a comparison today of mkyaffs2image and nanddump and noted >> that >> > a dump with nanddump had chunk sizes upto 4096 whereas the mkyaffs2image >> > was only 2048. >> > >> > the dump was of the /system mount with mkyaffs2image and the >> /dev/mtd/mtd5 >> > (system) for nanddump. >> > >> > I am confused can anyone help out here >> >> yaffs2 can use pretty much any chunk size you want and people regularly >> use >> 2k, 4k or other sizes (not necessarily 2^n). >> >> mkyaffs2image is set up to generate 2k chunks. If you want to change the >> NAND >> geometry then hack as you please. >> >> -- Charles >> >> >> _______________________________________________ >> yaffs mailing list >> yaffs@lists.aleph1.co.uk >> http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs >> > >