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 14:35:35 -0700 [thread overview]
Message-ID: <001101c6a6c4$471b9a70$a134800a@RudiDell> (raw)
Apologies if this should go to the patches list.
This change gets u-boot to skip bad blocks during an erase operation instead
of giving up.
Comments?
-DB
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nand_base.c.patch
Type: application/octet-stream
Size: 848 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20060713/38e1e905/attachment.obj
next reply other threads:[~2006-07-13 21:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 21:35 David Byron [this message]
2006-07-13 21:48 ` [U-Boot-Users] skipping bad blocks when erasing nand Wolfgang Denk
-- 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-17 21:42 David Byron
2006-07-20 23:22 ` Tolunay Orkun
2006-07-21 4:27 ` Stefan Roese
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='001101c6a6c4$471b9a70$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox