From: olea@hispafuentes.com
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: A question about FAT, FTL and MTD
Date: Tue, 07 Aug 2001 20:27:56 +0200 [thread overview]
Message-ID: <3B70332C.A9F3D944@hispafuentes.com> (raw)
The FTL related documentation I've read talks about a FAT interface to
flash chips but I'm confused because I didn't found any statement about
FAT is part of the FTL standard or not and because I didn't found a
reference to FAT in the MTD code/docs.
Can anybody confirm me if FAT is part of the FTL standard? If yes, how
is it supposed to be used with MTD?
If not, what can be needed to do that? As we have a flash NAND memory
on board, maybe it'd need a nftl driver similar to the DOC one. Correct
me if I'm wrong.
I understood that JFFS2 is a better tuned option for FS than FAT, but
we had a legacy FAT system and it could be useful to maintain the DOS
media compatibility if possible, and we want to be sure what design
options we have.
Again, thanks for your time :-)
--
A.Ismael Olea González
tlf +(34) 914 575 330
mailto:olea@hispafuentes.com
reply other threads:[~2001-08-07 18:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B70332C.A9F3D944@hispafuentes.com \
--to=olea@hispafuentes.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox