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 12:53:46 -0600	[thread overview]
Message-ID: <4B75A3BA.8000501@freescale.com> (raw)
In-Reply-To: <27567768.post@talk.nabble.com>

Steven Zedeck wrote:
> First of all, I inherited much of this code, especially the NAND-related
> stuff. I've never needed to go into this portion of the code.
> 
> It seems we are using the mtd driver as all our files dealing with nand are
> in drivers/mtd/nand. The only place I see NAND_USE_FLASH_BBT being used is
> in nand_bbt.c in nand_default_bbt. I see this:
> 
> this->options |= NAND_USE_FLASH_BBT;
> return nand_scan_bbt (mtd, &agand_flashbased);
> 
> Is this what you are referring to?

No, I mean in the NAND driver for your specific hardware 
(fsl_elbc_nand.c, mxc_nand.c, ndfc_nand.c, etc).

> Also, once we get the BBT created, does the code that loads Linux use that
> info ?

The BBT is created on the flash.  Linux runs pretty much the same code 
as u-boot and will use the on-flash BBT if its NAND driver specifies 
NAND_USE_FLASH_BBT.  This isn't about in-memory BBTs.

-Scott

  reply	other threads:[~2010-02-12 18:53 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
2010-02-12 18:47         ` Steven Zedeck
2010-02-12 18:53           ` Scott Wood [this message]
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=4B75A3BA.8000501@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