From: tglx@linutronix.de (Thomas Gleixner)
To: linux-mtd@lists.infradead.org
Subject: copy filesystem to nand flash without ecc
Date: Thu, 13 Feb 2003 17:52:54 +0100 [thread overview]
Message-ID: <200302131752.54716.tglx@linutronix.de> (raw)
In-Reply-To: <4EF56021.2C81712E.0265FBE9@netscape.net>
On Thursday 13 February 2003 12:16, Kschoo70C at netscape.net wrote:
> Hi,
> I notice some update on the JFFS2 out of band usage in
> http://www.linux-mtd.infradead.org/tech/nand.html,
> whereby the offset 0x4 used to be ECC valid marker has been made obsolete.
> In this case, if I write a jffs image to the mtd device without adding the
> ECC in the out of band area, the nand driver will not know about that. The
> question here is, what is the consequence of writing an image without
> adding the ecc to the out of band area ? Isn't it true the jffs2 file
> system always uses read_ecc and write_ecc when the flash type is nand ?
True.
You will get a endless bunch of ECC failure warnings. They will go away,
if you copy files around. As ECC is essential for NAND, we removed the
non ECC stuff for JFFS2 :)
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx at linutronix.de
next prev parent reply other threads:[~2003-02-13 16:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 11:16 copy filesystem to nand flash without ecc Kschoo70C at netscape.net
2003-02-13 16:52 ` Thomas Gleixner [this message]
2003-02-14 8:59 ` David Woodhouse
2003-02-14 9:03 ` Thomas Gleixner
2003-02-14 17:10 ` Alex Samoutin
2003-02-14 22:37 ` Thomas Gleixner
2003-02-15 0:13 ` David Woodhouse
2003-02-17 12:36 ` kokseng choo
2003-02-17 15:37 ` Thomas Gleixner
2003-02-17 15:02 ` kokseng choo
2003-02-17 16:02 ` kokseng choo
2003-02-17 22:30 ` Charles Manning
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=200302131752.54716.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox