From: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] mips: Call 'nand_init()' in generic board initialization when CONFIG_CMD_NAND is set
Date: Sat, 17 May 2008 01:26:27 +0900 [thread overview]
Message-ID: <482DB5B3.7030800@ruby.dti.ne.jp> (raw)
In-Reply-To: <1210861819-28024-1-git-send-email-mcmullan@netapp.com>
Hi Jason,
Jason McMullan wrote:
> diff --git a/lib_mips/board.c b/lib_mips/board.c
> index 1645f2c..e33070d 100644
> --- a/lib_mips/board.c
> +++ b/lib_mips/board.c
> @@ -28,6 +28,7 @@
> #include <version.h>
> #include <net.h>
> #include <environment.h>
> +#include <nand.h>
This will break build. According to the blackfin, we can't even include
<nand.h> if it's not configured.
http://git.denx.de/?p=u-boot.git;a=blob;f=lib_blackfin/board.c;h=43d8be8e21f25e37e7ade0eea86549b125775152;hb=a38dc3ea8614f8b0c41e432b445a9959b9711295#l25
# by the way, all ARCHs which need nand_init() should include <nand.h>
in the same way as blackfin, shouldn't they?
>
> DECLARE_GLOBAL_DATA_PTR;
>
> @@ -416,6 +417,11 @@ void board_init_r (gd_t *id, ulong dest_addr)
> }
> #endif
>
> +#ifdef CONFIG_CMD_NAND
> + puts("NAND: ");
> + nand_init(); /* go init the NAND */
> +#endif
> +
> #if defined(CONFIG_MISC_INIT_R)
> /* miscellaneous platform dependent initialisations */
> misc_init_r ();
I'm not familiar with NAND, so don't know that above is a good timing to
call nand_init(). If this works for you, I'm fine ATM.
Thanks!
Shinya
next prev parent reply other threads:[~2008-05-16 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 14:30 [U-Boot-Users] [PATCH] mips: Call 'nand_init()' in generic board initialization when CONFIG_CMD_NAND is set Jason McMullan
2008-05-16 16:26 ` Shinya Kuribayashi [this message]
2008-05-16 18:39 ` [U-Boot-Users] [PATCH] mips: Call 'nand_init()' in genericboard " McMullan, Jason
2008-05-16 19:32 ` [U-Boot-Users] [PATCH] mips: Call 'nand_init()' in generic board " Scott Wood
2008-05-17 1:07 ` Shinya Kuribayashi
2008-05-22 14:50 ` Shinya Kuribayashi
-- strict thread matches above, loose matches on Subject: below --
2008-05-15 14:08 Jason McMullan
2008-05-15 14:08 ` Jason McMullan
2008-05-15 14:14 ` 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=482DB5B3.7030800@ruby.dti.ne.jp \
--to=skuribay@ruby.dti.ne.jp \
--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