From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] skipping bad blocks when erasing nand
Date: Fri, 21 Jul 2006 06:27:40 +0200 [thread overview]
Message-ID: <200607210627.41450.sr@denx.de> (raw)
In-Reply-To: <44C0101E.1090505@orkun.us>
Hi Tolunay,
On Friday 21 July 2006 01:22, Tolunay Orkun wrote:
> 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.
Good idea.
> 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?
I would also prefer this kind of implementation. Just my $0.02.
Best regards,
Stefan
next prev parent reply other threads:[~2006-07-21 4:27 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
2006-07-21 4:27 ` Stefan Roese [this message]
-- 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=200607210627.41450.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox