Reduce boot time with jffs2 and CM-X255
Artem Bityutskiy
dedekind at infradead.org
Wed Dec 20 04:41:09 EST 2006
On Wed, 2006-12-20 at 10:17 +0100, Ricard Wanderlof wrote:
> Admittedly, NAND
> is faster than NOR, but then you've got quite a lot of empty flash too
> (250 MB).
Just do not include empty eraseblocks to the image.
> I don't know what the solution is - one idea is that a program like
> nandwrite could be instructed to write cleanmarkers to the OOB of unused
> parts of a partition. Currently there is no support for this but it could
> be added.
nandwrite -o ?
>
> Hm, sidetracking here a bit, I'm thinking a general erase + write image
> utility for NAND flash would be useful, given that bad block management
> gets a bit hairy when you write to NAND and the write fails - should the
> block be re-erased (not really part of a nand writing tool's job) and
> retried, or just marked as bad (because most likely the block had recently
> been erased by an erasing tool)? Having erase+write in the same tool would
> make it easier for the tool to manage this, and it could also write jffs2
> cleanmarkers to the oob as part of the whole procedure.
I would recommend to improve/re-work/upgrade nandwrite instead of a new
tool.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
More information about the linux-mtd
mailing list