All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jim Zeus" <jimzeus@vip.sina.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: MTD mail list <linux-mtd@lists.infradead.org>
Subject: Re: [SPAM] FAT on NAND
Date: Mon, 7 Apr 2003 11:19:53 +0800	[thread overview]
Message-ID: <004a01c2fcb4$8f61cf60$2a00a8c0@zhengjun> (raw)
In-Reply-To: 1049449251.1980.90.camel@passion.cambridge.redhat.com

> > 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:
> 
> Windows won't recognise raw NAND flash anyway. You'll have to write
> _some_ kind of driver for Windows.
> 

Since the MTD block device(which include nand.c,mtdcore.c 
and mtdblock.c) is a block device, why I can't build
any filesystem on it? 
And, what's the difference between MTD block device and NFTL
if they stay on the same layer? Even though I cant use NFTL
because of some "silly patent problem" ,I still wanna know it,
thanks.


> > 1.How unstable would it be? Does it support: 
> >      a.journaling (crash/power-off safe ,I mean)
> 
> No.
> 
> >      b.bad block management
> 
> No.
> 
> >      c.wear levelling
> 
> No.
> 
> >      d.error correction
> 
> No.
> 
> >      e.something else I dont know to make the FS reliable
> 
> No.

Then, maybe the lower layer (MTD or NFTL) support it? or all the
stuff(a.b.c.d.e) are supported only by the file system 
(JFFS2/YAFFS,I mean)?

> 
> > 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 ?
> 
> I told you to use the SmartMedia format, not NFTL. You can do that on
> any NAND hardware; NFTL has silly patent problems in some parts of the
> world.

Thank you, but what is the SmartMedia format? Sorry I am not 
familiar with that.

> 
> But really you should have a file system directly on the flash, not a
> translation layer pretending to be a block device.
> 

Do you mean build a totally new FS on a _bare_ NAND flash or on a MTD? 
You are so right, but I must build a FS which Windows can 
recognize and I have no enough time to do this before the time
limit.


> > 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?
> 
> It's not reliable, as you were told.
> 
> > BTW:Why my mail sent to the maillist always "awaits moderator approval"?
> 
> The ones you send as HTML get bounced for that reason. The rest are
> trapped because SpamAssassin doesn't like them...

I think my mail is txt but not in HTML.Whatever, I hope it won't 
happen anymore:)

> 
> X-Spam-Status: Yes, hits=7.7 required=5.0
>         tests=AWL,NO_REAL_NAME,RCVD_IN_OSIRUSOFT_COM,RCVD_IN_RFCI,
>         SPAM_PHRASE_00_01,X_OSIRU_SPAM_SRC version=2.44
> 
> -- 
> dwmw2
> 
> 
> 

  reply	other threads:[~2003-04-07  3:21 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 [this message]
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='004a01c2fcb4$8f61cf60$2a00a8c0@zhengjun' \
    --to=jimzeus@vip.sina.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 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.