public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Jason Chan <jason@emsoftltd.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Bad Block management routine for MTD NandFlash driver?
Date: Mon, 17 Jun 2002 09:41:50 +0100	[thread overview]
Message-ID: <19294.1024303310@redhat.com> (raw)
In-Reply-To: <3D0D9DA9.6090404@emsoftltd.com>

jason@emsoftltd.com said:
>     I trying to use EXT2 for my nandflash driver. Is that OK? 

No. You need _some_ kind of file system which is capable of dealing with 
flash -- either a real file system directly on the flash such as JFFS2, or 
a 'translation layer' like the SmartMedia one or NFTL if you really need to 
use ext2 for some reason.

--
dwmw2

  reply	other threads:[~2002-06-17  8:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-17  8:04 Bad Block management routine for MTD NandFlash driver? Jason Chan
2002-06-17  8:22 ` David Woodhouse
2002-06-17  8:28   ` Jason Chan
2002-06-17  8:41     ` David Woodhouse [this message]
2002-06-17  8:43       ` Jason Chan
2002-06-17  9:03         ` David Woodhouse

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=19294.1024303310@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=jason@emsoftltd.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