From: <jimzeus@vip.sina.com>
To: linux-mtd@lists.infradead.org
Subject: [SPAM] FAT on NAND
Date: Fri, 04 Apr 2003 14:21:36 +0800 [thread overview]
Message-ID: <20030404062136.7806.qmail@vip.sina.com> (raw)
Hi, all:
What I am doing now is to build a filesystem which can be
recognized on _raw_ NAND flash. So, I think FAT will be the only
choice(though I know it's very unstable). And I have following question now:
1.How unstable would it be? Does it support:
a.journaling (crash/power-off safe ,I mean)
b.bad block management
c.wear levelling
d.error correction
e.something else I dont know to make the FS reliable
2.I have checked the NAND flash docoment (especially
the "Filesystems supporting NAND"chapter) and I found out that
it seems no way to build a FAT on a bare NAND flash but only on
the SmartMediaCards, am I right? Or the SM card and the bare NAND
are just the same thing when a FAT on it.
3.Maybe I misunderstood,but David Woodhouse had told me that I should apply layers like FAT->NFTL->NAND if I wanna build a FAT on
a NAND flash.But I learned that the NFTL only support Doc from the
NAND flash document, isnt it? And what should I do to support the
FAT ?
4.Everybody tells me that the Fat on a NAND is not reliable,but I
think USB mass storage are based on NAND and got a FAT (or some
filesystem which windows can recognize) on it, so ,how comes it
happen?
BTW:Why my mail sent to the maillist always "awaits moderator approval"?
TIA
Jim Zeus
______________________________________
===================================================================
next reply other threads:[~2003-04-04 6:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 6:21 jimzeus [this message]
2003-04-04 9:40 ` [SPAM] FAT on NAND David Woodhouse
2003-04-07 3:19 ` Jim Zeus
2003-04-07 14:32 ` Jörn Engel
2003-04-07 22:49 ` Charles Manning
2003-04-04 10:48 ` Thomas Gleixner
2003-04-07 3:32 ` Jim Zeus
2003-04-07 8:01 ` Thomas Gleixner
2003-04-04 20:08 ` 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=20030404062136.7806.qmail@vip.sina.com \
--to=jimzeus@vip.sina.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.