From: Thomas Gleixner <tglx@linutronix.de>
To: jimzeus@vip.sina.com, linux-mtd@lists.infradead.org
Subject: Re: [SPAM] FAT on NAND
Date: Fri, 04 Apr 2003 12:48:57 +0200 [thread overview]
Message-ID: <200304041248.57751.tglx@linutronix.de> (raw)
In-Reply-To: <20030404062136.7806.qmail@vip.sina.com>
On Friday 04 April 2003 08:21, jimzeus@vip.sina.com wrote:
> 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:
For what ? Why don't you use JFFS2 or YAFFS, which handle NAND out of the box
?
> 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
JFFS2 and YAFFS have all this, read the source and build a new one, if you
have enough time.
> 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.
SMCard and bare NAND is just the same, only packaging is different
> 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 ?
Hack NTFL :)
> 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?
Yes, this is Smart-Media-FAT, which is not exactly the same as DOS-FAT.
SmartMedia-FAT is used on SmartMedia cards for MP3-Players, Digicams ...
There exist various adapters (USB, serial, LPT) to access it via a PC.
SmartMedia-FAT is designed for NAND-FLASH and handles bad block management
and error correction.
If you want compability to this, you have to write a fs-driver, which is
compatible to the SMART-Media-FAT definition, which is available from Toshiba
under a non disclosure aggreement.
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
next prev parent reply other threads:[~2003-04-04 9:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 6:21 [SPAM] FAT on NAND jimzeus
2003-04-04 9:40 ` 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 [this message]
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=200304041248.57751.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox