From: Jason Chan <jason@emsoftltd.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Bad Block management routine for MTD NandFlash driver?
Date: Mon, 17 Jun 2002 16:28:25 +0800 [thread overview]
Message-ID: <3D0D9DA9.6090404@emsoftltd.com> (raw)
In-Reply-To: 18852.1024302161@redhat.com
David,
I trying to use EXT2 for my nandflash driver. Is that OK?
When I make a EXT2 file system on the nandflash driver, the
mtd/nand/nand.c show a error message that "nand_erase: Failed erase",
and it keep looping the same statement.
Since I may use other filesystem in the future, eg. CRAMFS or VFAT, I
have no idea on the completeness of the filesystem on the bad block
managment. So how can enable use the translation layer to manage my bad
block?
David Woodhouse wrote:
>jason@emsoftltd.com said:
>
>> Any bad block management routine (eg. Invalid block table ) is
>>implemented for MTD NandFlash driver? It seems that the ECC routine is
>>not enough for my nandflash driver. And I need a more robust bad
>>block management routine for that.
>>
>
>The low-level hardware driver does not implement and bad block management.
>That is done by whatever file system or translation layer you use on the
>flash. What are you intending to use? JFFS2?
>
>--
>dwmw2
>
>
--
Best Regards,
Jason Chan
Emsoft Ltd.
next prev parent reply other threads:[~2002-06-17 8:34 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 [this message]
2002-06-17 8:41 ` David Woodhouse
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=3D0D9DA9.6090404@emsoftltd.com \
--to=jason@emsoftltd.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.