From: eddy@emsoftltd.com (Eddy Yeung)
To: linux-mtd@lists.infradead.org
Subject: Help on bad block table handling
Date: Thu, 27 Feb 2003 16:14:09 +0800 [thread overview]
Message-ID: <3E5DC8D1.9000900@emsoftltd.com> (raw)
Hi,
I have questions about the bad block table handling on nand flash with
ext2. Do you update the bad block table when you have erase and program
failures? The implementation that I am having creates the bad block
table only when the flash is being formated. That is, there will be no
updating of the bad block table until next formating of the flash.
Should I update the bad block table when erase and program failures are
detected? Does anyone know whether there is an implementation for that?
Please advise!! Thank you.
Best regards,
Eddy
eddy at emsoftltd.com
reply other threads:[~2003-02-27 8:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3E5DC8D1.9000900@emsoftltd.com \
--to=eddy@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