From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] NAND search for bad blocks on startup
Date: Mon, 08 May 2006 22:13:44 +0200 [thread overview]
Message-ID: <20060508201344.CEA0B353A57@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 08 May 2006 11:46:43 PDT." <200605081846.k48IkhDL017032@xdr.com>
In message <200605081846.k48IkhDL017032@xdr.com> you wrote:
>
> 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.
Don't enable NAND support in your board config file until the other
areas in your code are debugged; then enable it when you want to get
NAND working.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Fools ignore complexity. Pragmatists suffer it. Some can avoid it.
Geniuses remove it.
- Perlis's Programming Proverb #58, SIGPLAN Notices, Sept. 1982
next prev parent reply other threads:[~2006-05-08 20:13 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
2006-05-08 20:13 ` Wolfgang Denk [this message]
-- 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=20060508201344.CEA0B353A57@atlas.denx.de \
--to=wd@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