public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Kyungmin Park <kyungmin.park@samsung.com>
To: Adrian Hunter <ext-adrian.hunter@nokia.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: OneNAND: Always print error messages
Date: Fri, 19 Jan 2007 08:21:12 +0000 (GMT)	[thread overview]
Message-ID: <7109995.92931169194871882.JavaMail.weblogic@ep_ml26> (raw)




------- Original Message -------
Sender : Adrian Hunter<ext-adrian.hunter@nokia.com> 
Date   : Jan 19, 2007 17:02
Title  : Re: OneNAND: Always print error messages

ext Kyungmin Park wrote:
>> Is it possible to get an ECC error when scanning a bad block?
> 
> Theoretical it's possible but I never see it.

I like to program all the corner cases.

>> 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.

Thank you,
Kyungmin Park




             reply	other threads:[~2007-01-19  8:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19  8:21 Kyungmin Park [this message]
2007-01-19  8:58 ` OneNAND: Always print error messages Adrian Hunter
  -- 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=7109995.92931169194871882.JavaMail.weblogic@ep_ml26 \
    --to=kyungmin.park@samsung.com \
    --cc=ext-adrian.hunter@nokia.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