From: Adrian Hunter <ext-adrian.hunter@nokia.com>
To: kyungmin.park@samsung.com
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: OneNAND: Always print error messages
Date: Thu, 18 Jan 2007 18:24:24 +0200 [thread overview]
Message-ID: <45AF9F38.9040602@nokia.com> (raw)
In-Reply-To: <5309548.532541169078227711.JavaMail.weblogic@ep_ml22>
ext Kyungmin Park wrote:
> Yes, simple solution is separate read oob from normal and scanning.
> I think is is easy because we can use state variable, FL_SCANNING instead of FL_READING in bbt.
Also there are the issues of a load error or ECC error when scanning for bad blocks:
Is it possible to get an ECC error when scanning a bad block?
If a load error occurs when scanning a bad block, does that mean the dataRAM
has been updated or not?
next prev parent reply other threads:[~2007-01-18 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 23:57 OneNAND: Always print error messages Kyungmin Park
2007-01-18 1:34 ` Artem Bityutskiy
2007-01-18 16:24 ` Adrian Hunter [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-19 8:21 Kyungmin Park
2007-01-19 8:58 ` Adrian Hunter
2007-01-19 7:14 Kyungmin Park
2007-01-19 8:02 ` Adrian Hunter
2007-01-12 6:48 Kyungmin Park
2007-01-17 23:14 ` Artem Bityutskiy
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=45AF9F38.9040602@nokia.com \
--to=ext-adrian.hunter@nokia.com \
--cc=kyungmin.park@samsung.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