From: tglx@linutronix.de (Thomas Gleixner)
To: David Daney <ddaney@avtrex.com>, linux-mtd@lists.infradead.org
Subject: Re: mtd, mtdblock and nand ecc.
Date: Wed, 14 Apr 2004 14:43:56 +0200 [thread overview]
Message-ID: <200404141443.56257.tglx@linutronix.de> (raw)
In-Reply-To: <407CC018.3030505@avtrex.com>
On Wednesday 14 April 2004 06:37, David Daney wrote:
> Is there some reason that the mtd and mtdblock drivers do not use ECC
> when the backing device is nand with ECC enabled?
Yes.
If the oobsel structure == NULL, then the nand driver uses the structure,
which is associated to this mtd device. This can be done from userspace using
MEMSETOOBSEL ioctl.
NAND aware filesystem drivers provide their own oobsel structure and use the
xxx_ecc functions.
> I suppose you could run into problems if the backing device were a
> concatenation of ECC and non-ECC devices, but that could probably be
> detected either on open or at each page read/write.
Concatenation of NAND and NOR will not work anyway, as the fs must be aware of
the FLASH type.
--
Thomas
________________________________________________________________________
"Free software" is a matter of liberty, not price. To understand the concept,
you should think of "free" as in "free speech,'' not as in "free beer".
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
next prev parent reply other threads:[~2004-04-14 12:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 4:37 mtd, mtdblock and nand ecc David Daney
2004-04-14 12:43 ` Thomas Gleixner [this message]
2004-04-14 14:11 ` David Daney
2004-04-14 14:48 ` Thomas Gleixner
2004-04-14 15:13 ` David Daney
2004-04-14 16:15 ` Thomas Gleixner
2004-04-14 16:49 ` David Daney
2004-04-14 17:36 ` Thomas Gleixner
2004-04-14 18:39 ` David Daney
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=200404141443.56257.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=ddaney@avtrex.com \
--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