From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] skipping bad blocks when erasing nand
Date: Thu, 20 Jul 2006 18:22:06 -0500 [thread overview]
Message-ID: <44C0101E.1090505@orkun.us> (raw)
In-Reply-To: <003a01c6a9e9$f371bf70$a134800a@RudiDell>
David Byron wrote:
> On Friday, July 14th, Wolfgang Denk wrote:
>
>> I tend to agree here, which was the reason that I said I was willing
>> to accept the patch, but that at least the printf() shoould be kept
>> so that the user gets the warning.
>
> Sorry for the delay. Here's a patch that lets the erase continue, but does
> print a message.
Instead of printing a message for each block, I think it would be neater
to give a summary at the end like:
x blocks erased successfully. y blocks ignored.
nand bad command gives the list anyway if someone is more inclined to
find out what blocks.
What do you (and Wolfgang) think about my proposal?
Tolunay
next prev parent reply other threads:[~2006-07-20 23:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 21:42 [U-Boot-Users] skipping bad blocks when erasing nand David Byron
2006-07-20 23:22 ` Tolunay Orkun [this message]
2006-07-21 4:27 ` Stefan Roese
-- strict thread matches above, loose matches on Subject: below --
2006-07-13 22:21 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
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
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=44C0101E.1090505@orkun.us \
--to=listmember@orkun.us \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox