public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: tglx@linutronix.de (Thomas Gleixner)
To: linux-mtd@lists.infradead.org
Subject: Initialising NAND OOB with Software ECC
Date: Fri, 14 Feb 2003 14:02:53 +0100	[thread overview]
Message-ID: <200302141402.53443.tglx@linutronix.de> (raw)
In-Reply-To: <200302141136.29775.phil@river-bank.demon.co.uk>

On Friday 14 February 2003 12:36, Phil Thompson wrote:
> What about the other elements of struct mtd_oob_buf, ie. start and ptr?
Ok, I forgot start.
> What about a pointer to the oob buffer?
I see, we need data too. :)
But then we should add two pointers, so you can hold two different buffers 
from userspace.
truct nand_ctrl {
	int	start;			// startadress 
	int	oob_select;	// selector for OOB usage
 	int	data_lenght;	// length of data
 	int	oob_length;	// length of oob-buffer
	int	data_ptr;		// pointer to data buffer
	int	oob_ptr;		// pointer to oob buffer
};

> > JFFS2 needs no oob buffer for write, but YAFFS does.
> JFFS2 doesn't need one for read either does it?
No, you can just use it if you're curious or, if you want to read a complete 
image with oob-data included, which could be useful for debugging ....

-- 
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx at linutronix.de

  reply	other threads:[~2003-02-14 13:02 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 [this message]
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=200302141402.53443.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