From: tglx@linutronix.de (Thomas Gleixner)
To: linux-mtd@lists.infradead.org
Subject: Initialising NAND OOB with Software ECC
Date: Fri, 14 Feb 2003 15:06:17 +0100 [thread overview]
Message-ID: <200302141506.17642.tglx@linutronix.de> (raw)
In-Reply-To: <1045230987.22719.59.camel@passion.cambridge.redhat.com>
On Friday 14 February 2003 14:56, David Woodhouse wrote:
> On Fri, 2003-02-14 at 13:50, Thomas Gleixner wrote:
> > True, doe you have a better idea ?
>
> We don't _really_ need to write both in a single atomic operation, do
> we? Write to two different devices. You can always provide a library
> routine to do the right thing if you really care about upsetting the
> userspace programmer.
I would like to do it in one go, as we calc ECC and put it into the supplied
buffer, which comes either from kernel or from userspace. You should have the
same functionality in userspace than in kernel space.
With two devices, who have two operations, which can get out of sync. Not a
really good idea IMHO. Such a interface would be useful to test and debug
filesystems from userspace. So you can use the same functionality as if you
are in the kernel.
--
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 14:06 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
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 [this message]
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=200302141506.17642.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