From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steven Zedeck <saz@proliphix.com>
Date: Fri, 12 Feb 2010 11:18:55 -0800 (PST)
Subject: [U-Boot] [PATCH] add explicit bbt creation to commandline
In-Reply-To: <4B75A3BA.8000501@freescale.com>
References: <20080706080456.GF4167@prithivi.gnumonks.org>
	<27558231.post@talk.nabble.com>
	<20100212170411.GA21800@loki.buserror.net>
	<27566937.post@talk.nabble.com> <4B759454.8070906@freescale.com>
	<27567768.post@talk.nabble.com> <4B75A3BA.8000501@freescale.com>
Message-ID: <27568153.post@talk.nabble.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de



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

You have been so helpful. I looked at the mtd/nand/Makefile and the only
file that's included besides the nand* files is:

COBJS-y += fsl_upm.o

However, in that code:
#if defined(CONFIG_CMD_NAND) && defined(CONFIG_NAND_FSL_UPM)

But I don't see CONFIG_NAND_FSL_UPM defined anywhere. It seems that this
file really isn't being used.

How do I determine what hadrware driver its using? I'm sure this sounds like
a dumb question. Do all the drivers live in drivers/mtd/nand/.... ?

thanks,
Steve

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