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: Fri, 19 Jan 2007 10:58:40 +0200 [thread overview]
Message-ID: <45B08840.6050507@nokia.com> (raw)
In-Reply-To: <7109995.92931169194871882.JavaMail.weblogic@ep_ml26>
ext Kyungmin Park wrote:
>>>> If a load error occurs when scanning a bad block, does that mean the dataRAM
>>>> has been updated or not?
>>> scanning a bad block means read oob so we don't update dataRAM. In onenand implementation. we always invalid dataRAM in oob case.
>>
>> I meant the dataRAM spare area: 8010h - 804fh in the bufferRAM address map.
>>
>> After a load error, will this:
>>
>> this->read_bufferram(mtd, ONENAND_SPARERAM, buf, column, thislen);
>>
>> read the what was meant to be loaded, or will it still contain the data from a previous load?
>
> => It depends on load error timings. but we think it is always invalid.
> load error means that there's error during load from nand core to bufferram.
So, when scanning for bad blocks, after a load error or ECC (2 bit) error, we have to
assume that the block is bad without reading the spare area?
In that case, should we attempt to mark the block as bad,
perhaps writing the spare area in the second page?
next prev parent reply other threads:[~2007-01-19 9:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 8:21 OneNAND: Always print error messages Kyungmin Park
2007-01-19 8:58 ` Adrian Hunter [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-19 7:14 Kyungmin Park
2007-01-19 8:02 ` Adrian Hunter
2007-01-17 23:57 Kyungmin Park
2007-01-18 1:34 ` Artem Bityutskiy
2007-01-18 16:24 ` 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=45B08840.6050507@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