public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Seongsu Lee <senux@senux.com>
To: linux-mtd@lists.infradead.org
Cc: Josh Boyer <jwboyer@gmail.com>
Subject: Re: FAT file system on NAND flash memory
Date: Fri, 27 Apr 2007 02:59:02 +0900	[thread overview]
Message-ID: <20070426175902.GA21492@pooky.senux.com> (raw)
In-Reply-To: <625fc13d0704120655u2f452b12ge9315f47b951aa34@mail.gmail.com>

On Thu, Apr 12, 2007 at 08:55:23AM -0500, Josh Boyer wrote:
> On 4/12/07, Seongsu Lee <senux@senux.com> wrote:
> > Hi,
> >
> > In my knowledge, mtdblock.c must be used to use
> > FAT filesystem on bare NAND flash memories
> > because NFTL is made only for a specific hardware,
> > DiskOnChip.
> >
> > (Layer 0) VFS
> > (Layer 1) FAT (or EXT2, EXT3)
> > (Layer 2) mtdblock.c (nftl.c can be used only with DiskOnChip)
> > (Layer 3) NAND flash memory driver (vendor specific)
> > (Layer 4) Physical NAND flash memory
> >
> > Please let me know if it is wrong.
> 
> That layering is correct, but your results will be bad.  mtdblock
> doesn't handle bad blocks.  So if you have one in the middle of your
> filesystem, it will break things.  You need some kind of translation
> layer if you're going to use NAND.

Thank you for the reply. 

Just one more question.

Could you tell me the reason that there is no translation layer code
in MTD for bare flash memories? 
(Because of patent or copyright? or technical reason? I wonder.)

-- 
Seongsu's personal blog - http://www.senux.com/
Beauty may be skin deep, but ugly goes clear to the
bone. -- Redd Foxx

  reply	other threads:[~2007-04-26 18:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-12 13:41 FAT file system on NAND flash memory Seongsu Lee
2007-04-12 13:55 ` Josh Boyer
2007-04-26 17:59   ` Seongsu Lee [this message]
2007-04-27 13:45     ` Josh Boyer
2007-04-27 12:50   ` Matthieu CASTET
2007-04-27 13:45     ` Josh Boyer
2007-05-29 17:09   ` Seongsu Lee

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=20070426175902.GA21492@pooky.senux.com \
    --to=senux@senux.com \
    --cc=jwboyer@gmail.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