From: tglx@linutronix.de (Thomas Gleixner)
To: linux-mtd@lists.infradead.org
Subject: Initialising NAND OOB with Software ECC
Date: Fri, 14 Feb 2003 10:05:54 +0100 [thread overview]
Message-ID: <200302141005.54498.tglx@linutronix.de> (raw)
In-Reply-To: <200302132020.02330.phil@river-bank.demon.co.uk>
On Thursday 13 February 2003 21:20, Phil Thompson wrote:
> What's the standard method for initialising the OOB area for software ECC
> when flashing a new JFFS2 image?
>
> The MEMWRITEDATA ioctl looks at first to be the method to use because it
> uses mtd->write_ecc(). However 0 (ie. NAND_ECC_NONE) is always passed as
> the last parameter which disables writing the ECC data. Wouldn't it be more
> flexible to allow user space to specify the OOB format in the ioctl? Or
> have another ioctl to support writing ECC data?
>
> I know I can use MEMWRITEOOB to write the data, but that means that I have
> to compute it in user space - which seems pointless given the kernel can do
> it.
True. I planned to make an ioctrl so you can write with the appropriate ECC
selector to NAND, but I hadnt hat the time to do so.
Poke me enough and maybe I find some time
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx at linutronix.de
next prev parent reply other threads:[~2003-02-14 9:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 20:20 Initialising NAND OOB with Software ECC Phil Thompson
2003-02-14 9:05 ` Thomas Gleixner [this message]
2003-02-14 9:46 ` Phil Thompson
2003-02-14 11:00 ` Thomas Gleixner
2003-02-14 11:36 ` Phil Thompson
2003-02-14 13:02 ` Thomas Gleixner
2003-02-14 13:14 ` David Woodhouse
2003-02-14 13:27 ` Thomas Gleixner
2003-02-14 13:36 ` David Woodhouse
2003-02-14 13:50 ` Thomas Gleixner
2003-02-14 13:56 ` David Woodhouse
2003-02-14 14:06 ` Thomas Gleixner
2003-02-14 14:18 ` Phil Thompson
2003-02-14 13:25 ` Phil Thompson
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=200302141005.54498.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