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: Check first or second pages for bad block information
Date: Mon, 22 Jan 2007 11:59:29 +0000 (GMT)	[thread overview]
Message-ID: <7065803.123891169467169423.JavaMail.weblogic@ep_ml23> (raw)

Hi, 


> I'm not sure we have to check 2nd page. Yes, Spec. says we will check 1st and 2nd ones.
> 
> It increase the boot time even though it's smaller one than others.

> My experience is that the OneNAND bad block scanning time is very small (i.e. insignicant) compared with overall boot time.
> For example:
>	2048 blocks x 2 pages x 30 microseconds per page = 0.12 seconds

I think it's big :). But if you don't mind.


> The specification says:
> 
> 	Check "FFFFh" at the 1st word of sector 0
> 	of spare area in 1st and 2nd page

> Based on the specification, I would presume that if a bad block goes un-noticed, it could be erased and written without error and only produc> e errors when the data is read back, by which time it is too late.

O.K., We follow the Spec.

I will commit your patch.

Thank you,
Kyungmin Park

             reply	other threads:[~2007-01-22 11:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-22 11:59 Kyungmin Park [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-22  7:33 OneNAND: Check first or second pages for bad block information Kyungmin Park
2007-01-22  8:45 ` Adrian Hunter
2007-01-22  9:13 ` 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=7065803.123891169467169423.JavaMail.weblogic@ep_ml23 \
    --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