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: Fri, 17 May 2002 09:19:20 -0700 (PDT) [thread overview]
Message-ID: <20020517161920.75017.qmail@web21505.mail.yahoo.com> (raw)
In-Reply-To: <2284.1021646359@redhat.com>
To use FAT filesystem for NAND flash i need :-
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)
am i right ? Please correct me as i am still learning
MTD's model.
yes, i can understand that NAND Flash Translation
Layer(NFTL) and Translation layer for FAT are in
different layers.
but is it possible to make FAT filesystem for NAND
flash like this :-
A. FAT: filesystem driver
B. Translation: translation layer on the NAND flash to
make it emulate a normal hard drive (with NFTL)
C. MTD: Memory Technology Devices driver (MTD Char)
D. NAND: generic NAND driver
E. Hardware specific driver (without NFTL)
Thank you for your help.
--- David Woodhouse <dwmw2@infradead.org> wrote:
>
> studying_mtd@yahoo.com said:
> > I was asking these question because you told me
> that i have to add
> > translation layer for FAT. what i was thinking
> that, is it possible
> > that if i write only one translation layer which
> will be good for FAT
> > as well as it will replace NFTL.
>
> I don't understand what you're trying to say. Please
> could you rephrase it,
> preferably not making any reference at all to FAT,
> ext2, reiserfs or
> anything else which is not relevant because it's
> handled by an entirely
> separate layer.
>
> --
> dwmw2
>
>
>
>
______________________________________________________
> Linux MTD discussion mailing list
>
http://lists.infradead.org/mailman/listinfo/linux-mtd/
__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com
next prev parent reply other threads:[~2002-05-17 16:25 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 [this message]
2002-05-18 16:00 ` David Woodhouse
2002-05-18 17:53 ` Studying MTD
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=20020517161920.75017.qmail@web21505.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