public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Studying MTD <studying_mtd@yahoo.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: FAT for NAND Flash
Date: Sat, 18 May 2002 10:53:06 -0700 (PDT)	[thread overview]
Message-ID: <20020518175306.38447.qmail@web21501.mail.yahoo.com> (raw)
In-Reply-To: <23649.1021737644@redhat.com>

Thank you very much for your correction.

I think, this should also be corrected :-

http://www.linux-mtd.infradead.org/tech/nand.html says
that :-

There are four layers of software

JFFS2: filesystem driver 
MTD: Memory Technology Devices driver 
NAND: generic NAND driver 
Hardware specific driver 

It should be :-

There are five layers of software

JFFS2: filesystem driver 
Flash Translation Layer: FTL (for NOR) or NFTL (for
NAND)
MTD: Memory Technology Devices driver 
NAND: generic NAND driver 
Hardware specific driver 

Am i again wrong ?

Thank you for your help.

--- David Woodhouse <dwmw2@infradead.org> wrote:
> 
> studying_mtd@yahoo.com said:
> > A. FAT: filesystem driver 
> > B. Translation: translation layer on the NAND
> flash to
> > make it emulate a normal hard drive
> > C. MTD: Memory Technology Devices driver (MTD
> Block)
> > D. NAND: generic NAND driver
> > E. Hardware specific driver (Plus NFTL)
> 
> No. NFTL _is_ the translation layer in (B). The
> SmartMedia format could be
> used in its place. The other list you gave looks
> more like the existing 
> situation.
> 


__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com

  reply	other threads:[~2002-05-18 17:53 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-16 14:14 FAT for NAND Flash Studying MTD
2002-05-16 14:24 ` David Woodhouse
2002-05-16 14:46   ` Studying MTD
2002-05-16 15:08     ` David Woodhouse
2002-05-16 16:31       ` Paul
2002-05-16 17:35         ` David Woodhouse
2002-05-16 20:34           ` Paul
2002-05-17  6:03             ` David Woodhouse
2002-05-17  6:40               ` Paul
2002-05-18  5:16     ` Yong-iL Joh
2000-01-12 11:37       ` Thomas Gleixner
2002-05-18  7:19       ` David Woodhouse
2002-05-19 23:58       ` FAT for NAND Flash --> Use of OOB Charles Manning
2002-05-17 13:44   ` FAT for NAND Flash Studying MTD
2002-05-17 13:50     ` David Woodhouse
2002-05-17 14:00       ` Studying MTD
2002-05-17 14:39         ` David Woodhouse
2002-05-17 16:19           ` Studying MTD
2002-05-18 16:00             ` David Woodhouse
2002-05-18 17:53               ` Studying MTD [this message]
2002-05-18 18:20               ` Studying MTD
2002-05-19  9:34                 ` David Woodhouse
2002-05-19 23:26                   ` Newby question Charles Manning
2002-05-20  6:49                     ` David Woodhouse
2002-05-20  7:48                       ` Newby question --> source tree management Charles Manning
2002-05-18  5:13 ` FAT for NAND Flash Yong-iL Joh
2002-05-18 15:30   ` Studying MTD
2002-05-20  3:39     ` Yong-iL Joh
2002-05-20 11:36       ` Studying MTD
2002-05-21 10:52         ` Yong-iL Joh
2002-05-21 22:36           ` Charles Manning

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=20020518175306.38447.qmail@web21501.mail.yahoo.com \
    --to=studying_mtd@yahoo.com \
    --cc=dwmw2@infradead.org \
    --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