All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Byron <dbyron@hheld.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] skipping bad blocks when erasing nand
Date: Thu, 13 Jul 2006 15:21:50 -0700	[thread overview]
Message-ID: <000001c6a6ca$bd0b3230$a134800a@RudiDell> (raw)
In-Reply-To: AAAAAJOKoN+ryO5OkOyypB2eX+6kDSEA

> Silently ignoring such errors without even  printing  a  message  and
> setting the return code of the command is not acceptable.

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
using nand chips.  If, for example, I want to erase a whole chip, then
silently skipping bad blocks seems like the way to go.  I could see keeping
some kind of debug message, but something less severe than KERN_WARNING.
Would that make this acceptable?

Thanks for your help.

-DB

             reply	other threads:[~2006-07-13 22:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13 22:21 David Byron [this message]
2006-07-13 22:45 ` [U-Boot-Users] skipping bad blocks when erasing nand Wolfgang Denk
2006-07-13 23:13   ` Dave Hylands
2006-07-14  7:10     ` Joachim Jaeger
2006-07-14  7:14   ` Stefan Roese
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='000001c6a6ca$bd0b3230$a134800a@RudiDell' \
    --to=dbyron@hheld.com \
    --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.