public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jim Zeus" <jimzeus@vip.sina.com>
To: <tglx@linutronix.de>
Cc: MTD mail list <linux-mtd@lists.infradead.org>
Subject: Re: [SPAM] FAT on NAND
Date: Mon, 7 Apr 2003 11:32:35 +0800	[thread overview]
Message-ID: <005001c2fcb6$553cf1a0$2a00a8c0@zhengjun> (raw)
In-Reply-To: 200304041248.57751.tglx@linutronix.de

> > 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 
> ?

Because I've got to build a FS which can be accessed by Windows and Linux at the same 
time.I think JFFS2/YAFFS can't be recognized by Windows nowadays. 
And , it seems like I have to support some device layer between the FS and Flash so the
Linux can access it, isn't it?
Is there anyway else I can choose?

> 
> > 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.

Are all the functions supported by JFFS2/YAFFS? Somebody told me the wear levelling
is supported by MTD

And It seems like I don't have enough time ,maybe I can finish it with all my leisure time.

> > 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. 

Does the SMART-Media-FAT build directly on a _bare_ NAND Flash ? 
If it is, That's nothing useful to me 'cause Linux cant access it.


Thanks a lot for answering my questions

Your Faithful
Jim Zeus




  reply	other threads:[~2003-04-07  3:33 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
2003-04-07  3:32   ` Jim Zeus [this message]
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='005001c2fcb6$553cf1a0$2a00a8c0@zhengjun' \
    --to=jimzeus@vip.sina.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.de \
    /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