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 18:14:51 -0800 (PST)	[thread overview]
Message-ID: <27571823.post@talk.nabble.com> (raw)
In-Reply-To: <4B75C6C0.8020706@freescale.com>




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.

  reply	other threads:[~2010-02-13  2:14 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
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 [this message]
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=27571823.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