All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <gleixner@autronix.de>
To: David Woodhouse <dwmw2@infradead.org>, gleixner@autronix.de
Cc: linux-mtd@lists.infradead.org, jffs-dev@axis.com
Subject: Re: JFFS2 & NAND
Date: Mon, 18 Feb 2002 10:48:33 +0100	[thread overview]
Message-ID: <02021810483303.00860@thomas> (raw)
In-Reply-To: <19529.1014024551@redhat.com>

On Monday, 18. February 2002 10:29, David Woodhouse wrote:
> gleixner@autronix.de said:
> > Yes inside JFFS2, but who tells the NAND driver, which layout to use.
>
> Do we really need the NAND driver to be able to use more than one layout?
>
> Either we have hardware ECC which determines the layout, or the NAND driver
> implements software ECC and gets to choose. Can't the filesystem just deal
> with the ECC layout used by the NAND driver, as determined by the
> underlying hardware?
Also hardware ECC does not determine the layout. It just builds the ECC, you 
have to read it out of the CLPD and write it at a appropriate place in the 
OOB area. Same on read.  
We can use a fixed layout for every chip-type. There are 2 good reasons not 
to do that.
1. The SMC DOS-FAT oob layout is more than ugly. To press our idea of oob 
usage into this, is like you slice a bread in many small pieces to fit into 
the subdivisions of your tupperbox, instead of rearanging the contents of the 
box.

2. I don't want to put too much restrictions into the oob layout, so we would 
make it hard for somebody, who want's to implement a different filesystem 
than JFFS2.

-- 
Thomas
__________________________________________________
Thomas Gleixner, autronix automation GmbH
auf dem berg 3, d-88690 uhldingen-muehlhofen
fon: +49 7556 919891 , fax: +49 7556 919886
mail: gleixner@autronix.de, http://www.autronix.de  

  reply	other threads:[~2002-02-18  9:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-14 15:57 JFFS2 & NAND Thomas Gleixner
2002-02-14 17:22 ` Peter De Schrijver
2002-02-14 17:27 ` David Woodhouse
2002-02-14 17:43   ` Thomas Gleixner
2002-02-17  9:51     ` David Woodhouse
2002-02-17 11:44       ` Thomas Gleixner
2002-02-17 17:25         ` David Woodhouse
2002-02-17 19:36           ` Thomas Gleixner
2002-02-18  8:48             ` Thomas Gleixner
2002-02-18  8:46               ` David Woodhouse
2002-02-18  9:26                 ` Thomas Gleixner
2002-02-18  9:29                   ` David Woodhouse
2002-02-18  9:48                     ` Thomas Gleixner [this message]
2002-02-18 16:02                       ` Thomas Gleixner

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=02021810483303.00860@thomas \
    --to=gleixner@autronix.de \
    --cc=dwmw2@infradead.org \
    --cc=jffs-dev@axis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.