From: David Ashley <uboot@xdr.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] NAND search for bad blocks on startup
Date: Sat, 6 May 2006 09:02:29 -0700 [thread overview]
Message-ID: <200605061602.k46G2T6b030445@xdr.com> (raw)
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?
I can confirm the newer NAND system works with a 16 bit Micron NAND flash
right out of the box once I've implemented the glue routines specific to my
board. Good job!
Before I knew about the newer git version and was modifying 1.1.4 I had
modified u-boot to support the micron NAND, but that work is irrelevant now.
Maybe u-boot is ready for a major new release 1.1.5???
-Dave
next reply other threads:[~2006-05-06 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 16:02 David Ashley [this message]
2006-05-08 9:50 ` [U-Boot-Users] NAND search for bad blocks on startup Wolfgang Denk
2006-05-08 18:46 ` David Ashley
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=200605061602.k46G2T6b030445@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