From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] What's the status on erasing a nand flash with bad blocks?
Date: Fri, 6 Oct 2006 21:43:42 +0200 [thread overview]
Message-ID: <200610062143.42500.sr@denx.de> (raw)
In-Reply-To: <45267230.7080107@orkun.us>
Hi Tolunay,
On Friday 06 October 2006 17:11, Tolunay Orkun wrote:
> > I would suggest that we change the current U-Boot code, so that erasing
> > doesn't stop at bad blocks anymore, but skips them and prints a message,
> > like the linux flash_eraseall utility:
> >
> > "Skipping bad block at 0x%08x"
>
> Last time we discussed this on the list I suggested we only print a
> summary at the end instead of for each skipped block. Summary would
> state how many bad blocks skipped during operation in all. We have
> another command to list the bad blocks (AFAIK) if one is interested at all.
OK.
I'll try to take a deeper look into the patch from Guido this weekend. Looks
promising.
Best regards,
Stefan
prev parent reply other threads:[~2006-10-06 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 15:04 [U-Boot-Users] What's the status on erasing a nand flash with bad blocks? mitsy
2006-10-06 12:26 ` Stefan Roese
2006-10-06 15:10 ` mitsy
2006-10-06 15:25 ` Guido Classen
2006-10-06 15:11 ` Tolunay Orkun
2006-10-06 19:43 ` Stefan Roese [this message]
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=200610062143.42500.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.