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 11:36:39 -0800 (PST) [thread overview]
Message-ID: <27568365.post@talk.nabble.com> (raw)
In-Reply-To: <27568153.post@talk.nabble.com>
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
>
> 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
>
>
I think we are just using the base/generic mtd nand driver. Is that
possible?
thanks,
Steve
--
View this message in context: http://old.nabble.com/-PATCH--add-explicit-bbt-creation-to-commandline-tp18299804p27568365.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
next prev parent reply other threads:[~2010-02-12 19:36 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 [this message]
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=27568365.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