On 2010-08-13, Grant Edwards grant.b.edwards@gmail.com wrote:
On 2010-07-09, Scott Wood scottwood@freescale.com wrote:
On Fri, Jul 09, 2010 at 08:56:40AM -0400, Ben Gardiner wrote:
If you are putting an MTD filesystem in that partition then the filesystem itself will take care of bad blocks that might occur in the partition during runtime. During the flash programming of this filesystem using nand write.jffs2 (or .e) will skip bad blocks that might occur in the partition.
If you are putting an image (kernel or initrd) into the partition then the 'nand read.e' and 'nand write.e' (as well as mtd-utils nandwrite) will handle bad blocks by skipping over them.
On any recent u-boot, the .jffs2/.e/.i suffixes are maintained for compatibility only -- bad block skipping is now the default behavior.
I'm using 1.3.4 (that's what's supported by Atmel). While that's the current "released" version, it appears to be over two years old?
Never mind. I see that the version naming scheme has changed and what I mistook for datestamped snapshots are actually released versions.
That said, 1.3.4 is the most recent version supported by Atmel. So my choices are try to port Atmels patches to a recent version or make do with the nand flash support in 1.3.4.