From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steven Zedeck <saz@proliphix.com>
Date: Fri, 12 Feb 2010 18:14:51 -0800 (PST)
Subject: [U-Boot] [PATCH] add explicit bbt creation to commandline
In-Reply-To: <4B75C6C0.8020706@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>
	<27568153.post@talk.nabble.com> <27568365.post@talk.nabble.com>
	<4B75C6C0.8020706@freescale.com>
Message-ID: <27571823.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




Scott Wood-2 wrote:
> 
> Steven Zedeck wrote:
>> 
>> 
>> Steven Zedeck wrote:
>>>
>>>> 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
> 
> You've got an old/out-of-tree u-boot.
> 
>> I think we are just using the base/generic mtd nand driver. Is that
>> possible?
> 
> No, there must be a controller driver.  It may be in a board or cpu 
> directory, though.  Search for board_nand_init().
> 
> 

Its in board/atmel/at91sam9rlek/nand.c

It doesn't do much but set up the various GPIO connections. Here's the
function:

int board_nand_init(struct nand_chip *nand)
{
	nand->ecc.mode = NAND_ECC_SOFT;
#ifdef CFG_NAND_DBW_16
	nand->options = NAND_BUSWIDTH_16;
#endif
	nand->cmd_ctrl = at91sam9rlek_nand_hwcontrol;
	nand->dev_ready = at91sam9rlek_nand_ready;
	nand->chip_delay = 20;

	return 0;
}

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