From: David Ashley <uboot@xdr.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] NAND search for bad blocks on startup
Date: Mon, 8 May 2006 11:46:43 -0700 [thread overview]
Message-ID: <200605081846.k48IkhDL017032@xdr.com> (raw)
In-Reply-To: <20060508095055.A315D353A57@atlas.denx.de>
>In message <200605061602.k46G2T6b030445@xdr.com> you wrote:
>> The newer NAND system seems to do a bad block search on startup.
>> This takes several seconds when the NAND is big, like 256Mbytes.
>> How about an #ifndef around this search, like CFG_NAND_NO_BAD_BLOCK_SEARCH
>> so it can be turned off?
>
>Do you think this is a good idea?
Hmmm. I guess I don't really understand the reasons why the nand bad was
done automatically on startup in the first place. I'm mainly just
speaking of during development -- 5-10 seconds additional delay on
each iteration of testing out u-boot adds up. So it would be nice to
be able to *not* do the nand bad intentionally at startup during
development.
Maybe the switch could exist, but after final code release always
don't activate it so it does the "nand bad" on startup as it
does now...
-Dave
next prev parent reply other threads:[~2006-05-08 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 16:02 [U-Boot-Users] NAND search for bad blocks on startup David Ashley
2006-05-08 9:50 ` Wolfgang Denk
2006-05-08 18:46 ` David Ashley [this message]
2006-05-08 20:13 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2006-05-06 16:03 David Ashley
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=200605081846.k48IkhDL017032@xdr.com \
--to=uboot@xdr.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