From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] calling nand_probe
Date: Mon, 20 Nov 2006 16:55:34 +0100 (MET) [thread overview]
Message-ID: <200611201656.41571.sr@denx.de> (raw)
In-Reply-To: <A590D28B5042C041BCC880094CB6172E33DF20@mail1irv.inside.istor.com>
Hi Charles,
On Monday 20 November 2006 16:34, Charles Krinke wrote:
> I need to use JFFS2 & NAND to boot a linux kernel. With that in mind, I
> define CFG_CMD_NAND & CFG_CMD_JFFS2.
>
> In looking through cmd_nand.c, I see the routine nand_probe which,
> amongs other things sets up the IO_ADDR member of the nand_chip
> structure.
>
> But, I don't see anywhere in the code base where nand_probe is called. I
> would have expected this to occur in the init_sequence[] array
> surrounded by an #ifdef CFG_CMD_NAND.
nand_probe() seems to be a function from the "legacy" NAND driver, which
should no longer be used. Please take a look how this is done in the "new"
NAND driver "drivers/nand/*". Examples to look at could be the pdnb3 board or
the PPChameleonEVB.
> Can you help me understand if nand_probe is called and if not, where
> should it be called. Additionally, any hints about other things to
> consider in this little sub-project would be greatly appreciated.
Please see above.
Best regards,
Stefan
PS: Again: Do not use the legacy NAND driver anymore. It's not supported
anymore and will eventually be deleted by Wolfgang in the future.
prev parent reply other threads:[~2006-11-20 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 15:34 [U-Boot-Users] calling nand_probe Charles Krinke
2006-11-20 15:55 ` Stefan Roese [this message]
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=200611201656.41571.sr@denx.de \
--to=sr@denx.de \
--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