From: Jamie Lokier <jamie@shareable.org>
To: Harald Welte <laforge@gnumonks.org>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
Artem Bityutskiy <dedekind1@gmail.com>,
Jin-Sung Yang <jsgood.yang@samsung.com>,
Ilho Lee <ilho215.lee@samsung.com>,
Marc Zyngier <marc.zyngier@tomtom.com>,
linux-mtd@lists.infradead.org, Nicolas Pitre <nico@cam.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [RFC] extending nand_ecclayout.eccpos once again
Date: Wed, 9 Sep 2009 12:56:33 +0100 [thread overview]
Message-ID: <20090909115633.GA1732@shareable.org> (raw)
In-Reply-To: <20090909111318.GD4771@prithivi.gnumonks.org>
Harald Welte wrote:
> Creating raw images? I'm also not sure how often that is being
> done. Why would you precompute an image with ECC and then write
> that to NAND rather than having the NAND layer generate the ECC
> while writing the image (like writing any other data)?
One reason is to be resistant to errors (such as RAM bit-flips) which
occur in flight from the time the data was read or generated (perhaps
a long time ago or far away), until it is written.
Such errors do happen, but it's a bit premature to start coding it in
MTD, as it would be far more valuable to have it in ordinary
filesystems and copying tools, and that looks quite a long way off :-)
-- Jamie
prev parent reply other threads:[~2009-09-09 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 9:30 [RFC] extending nand_ecclayout.eccpos once again Harald Welte
2009-09-08 6:13 ` Artem Bityutskiy
2009-09-08 15:28 ` Jamie Lokier
2009-09-08 17:26 ` Nicolas Pitre
2009-09-09 11:13 ` Harald Welte
2009-09-09 11:56 ` Jamie Lokier [this message]
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=20090909115633.GA1732@shareable.org \
--to=jamie@shareable.org \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=ilho215.lee@samsung.com \
--cc=jsgood.yang@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=laforge@gnumonks.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marc.zyngier@tomtom.com \
--cc=nico@cam.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.