From: Artem Bityutskiy <dedekind@infradead.org>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>
Subject: Re: Reduce boot time with jffs2 and CM-X255
Date: Wed, 20 Dec 2006 11:41:09 +0200 [thread overview]
Message-ID: <1166607669.3939.18.camel@sauron> (raw)
In-Reply-To: <Pine.LNX.4.64.0612201007240.11369@lnxricardw.se.axis.com>
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 (Битюцкий Артём)
next prev parent reply other threads:[~2006-12-20 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 16:25 Reduce boot time with jffs2 and CM-X255 Michel LECONTE
2006-12-20 7:16 ` Enrico Migliore
2006-12-20 8:38 ` Michel LECONTE
2006-12-20 8:53 ` Artem Bityutskiy
2006-12-20 9:06 ` Ricard Wanderlof
2006-12-20 9:15 ` Artem Bityutskiy
2006-12-20 9:17 ` Ricard Wanderlof
2006-12-20 9:41 ` Artem Bityutskiy [this message]
2006-12-20 9:46 ` Ricard Wanderlof
2006-12-20 12:16 ` Vitaly Wool
2006-12-21 8:12 ` Michel LECONTE
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1166607669.3939.18.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox