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 10:07:17 +0900 [thread overview]
Message-ID: <482E2FC5.6090609@ruby.dti.ne.jp> (raw)
In-Reply-To: <20080516193206.GA2795@loki.buserror.net>
Scott Wood wrote:
>> This will break build. According to the blackfin, we can't even include
>> <nand.h> if it's not configured.
>
> Let's fix that, then. What is the error?
mips-linux-gnu-gcc -g -Os -D__KERNEL__ -DTEXT_BASE=0xbfc00000 -I/home/skuribay/devel/u-boot.git/include -fno-builtin -ffreestanding -nostdinc -isystem /opt/codesourcery/mips-4.2/bin/../lib/gcc/mips-linux-gnu/4.2.3/include -pipe -DCONFIG_MIPS -D__MIPS__ -G 0 -mabicalls -fpic -msoft-float -march=r5500 -Wa,--trap -Wall -Wstrict-prototypes -c -o board.o board.c
In file included from /home/skuribay/devel/u-boot.git/include/nand.h:29,
from board.c:31:
/home/skuribay/devel/u-boot.git/include/linux/mtd/nand.h:413: error: 'NAND_MAX_CHIPS' undeclared here (not in a function)
make[1]: *** [board.o] Error 1
make[1]: Leaving directory `/home/skuribay/devel/u-boot.git/lib_mips'
make: *** [lib_mips/libmips.a] Error 2
skuribay at debian:~/devel/u-boot.git$
next prev parent reply other threads:[~2008-05-17 1:07 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
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 [this message]
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=482E2FC5.6090609@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