All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] skipping bad blocks when erasing nand
Date: Fri, 14 Jul 2006 09:14:07 +0200	[thread overview]
Message-ID: <200607140914.07427.sr@denx.de> (raw)
In-Reply-To: <20060713224545.0CD89353A2A@atlas.denx.de>

On Friday 14 July 2006 00:45, Wolfgang Denk wrote:
> In message <000001c6a6ca$bd0b3230$a134800a@RudiDell> you wrote:
> > I guess I don't understand what's going on enough then.  Is it really an
> > error to come across a bad block?  I thought that was part of the deal
> > when
>
> It should at least be reported to the user - otherwise he assumes  to
> have an error-free medium.

I am "voting" for David's implementation, since bad blocks are "normal" on 
NAND chips. And if I remember correctly, the "old" U-Boot NAND driver also 
just skipped the bad block upon erasing without reproting them.

Best regards,
Stefan

  parent reply	other threads:[~2006-07-14  7:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13 22:21 [U-Boot-Users] skipping bad blocks when erasing nand David Byron
2006-07-13 22:45 ` Wolfgang Denk
2006-07-13 23:13   ` Dave Hylands
2006-07-14  7:10     ` Joachim Jaeger
2006-07-14  7:14   ` Stefan Roese [this message]
2006-07-14  8:28     ` Wolfgang Denk
2006-07-14  8:47       ` Stefan Roese
2006-07-14  9:29         ` Wolfgang Denk
2006-07-14  9:58         ` Joachim Jaeger
2006-07-14 11:19           ` Wolfgang Denk
2006-08-22  9:44             ` Ladislav Michl
  -- strict thread matches above, loose matches on Subject: below --
2006-07-17 21:42 David Byron
2006-07-20 23:22 ` Tolunay Orkun
2006-07-21  4:27   ` Stefan Roese
2006-07-13 21:35 David Byron
2006-07-13 21:48 ` Wolfgang Denk

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=200607140914.07427.sr@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.