public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Steven Zedeck <saz@proliphix.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] add explicit bbt creation to commandline
Date: Fri, 12 Feb 2010 09:38:14 -0800 (PST)	[thread overview]
Message-ID: <27566937.post@talk.nabble.com> (raw)
In-Reply-To: <20100212170411.GA21800@loki.buserror.net>



> 
> Hi,
> I know this message is about 18 months old. I am using Uboot 2008.10,
> which
> seems to not include support for creating the Nand BBT (bad block table).
> Was this patch released and if so when? Forgive me as I don't know how to
> find out.
> 
> How best to add BBT support to Uboot? I need to have a BBT created such
> that
> Linux can use it when it loads.

> U-Boot supports creating a bad block table in flash, and has done so since
> before 2008.10 (assuming you're not using legacy NAND).  Whether it does
> this depends on whether the NAND driver requests it with NAND_BBT_CREATE
> in
> nand_bbt_descr.options and NAND_USE_FLASH_BBT in nand_chip.options.

I REALLY appreciate your help. I see in drivers/mtd/nand/nand_bbt.c where it
checks for NAND_BBT_CREATE. What I don't see is where/how this gets set. Is
there a config file that sets this?

thanks,
Steve

> Linux can also create this table.  Either way, it only needs to be done
> once, not on every boot.

> What the patch you quote does, as far as I can tell without what's been
> snipped, is allow a new bad block table to be created when erasing the
> entire chip.  Normally the bad block table would be excluded from a
> full-chip erase.


-- 
View this message in context: http://old.nabble.com/-PATCH--add-explicit-bbt-creation-to-commandline-tp18299804p27566937.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

  reply	other threads:[~2010-02-12 17:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-06  8:04 [U-Boot-Users] [PATCH] add explicit bbt creation to commandline Harald Welte
2008-07-06 11:16 ` Jean-Christophe PLAGNIOL-VILLARD
2008-07-06 13:31   ` Wolfgang Denk
2008-07-07 18:39 ` Scott Wood
2010-02-12  2:49 ` [U-Boot] " Steven Zedeck
2010-02-12 17:04   ` Scott Wood
2010-02-12 17:38     ` Steven Zedeck [this message]
2010-02-12 17:48       ` Scott Wood
2010-02-12 18:47         ` Steven Zedeck
2010-02-12 18:53           ` Scott Wood
2010-02-12 19:18             ` Steven Zedeck
2010-02-12 19:36               ` Steven Zedeck
2010-02-12 21:23                 ` Scott Wood
2010-02-13  2:14                   ` Steven Zedeck
2010-02-16 18:35                     ` Scott Wood
2010-02-17 15:38                       ` Steven Zedeck
2010-02-17 19:10                         ` Scott Wood

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=27566937.post@talk.nabble.com \
    --to=saz@proliphix.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