public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] add explicit bbt creation to commandline
Date: Fri, 12 Feb 2010 11:48:04 -0600	[thread overview]
Message-ID: <4B759454.8070906@freescale.com> (raw)
In-Reply-To: <27566937.post@talk.nabble.com>

Steven Zedeck wrote:
>> 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?

It is set in the BBT descriptor struct.  Which NAND driver are you 
using?  In order for it not to be set, the driver would have to use a 
non-default BBT descriptor (for bbt_td/bbt_md, not badblock_pattern) and 
leave out that flag.  I don't see any upstream drivers (at least not 
under drivers/mtd/nand) that do that, so it should just be a matter of 
whether the driver specifies NAND_USE_FLASH_BBT in chip->options.

-Scott

  reply	other threads:[~2010-02-12 17:48 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
2010-02-12 17:48       ` Scott Wood [this message]
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=4B759454.8070906@freescale.com \
    --to=scottwood@freescale.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