From: "Grant Likely" <grant.likely@secretlab.ca>
To: biovore <biovore@biovore.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: New to ML-310
Date: Wed, 13 Jun 2007 20:39:51 -0600 [thread overview]
Message-ID: <fa686aa40706131939p75e168a8hfe626e5452261c1f@mail.gmail.com> (raw)
In-Reply-To: <200706132031.53942.biovore@biovore.net>
On 6/13/07, biovore <biovore@biovore.net> wrote:
> CC arch/ppc/syslib/xilinx_pic.o
> arch/ppc/syslib/xilinx_pic.c:30:5: warning: "XPAR_XINTC_USE_DCR" is not
> defined
> arch/ppc/syslib/xilinx_pic.c:121:5: warning: "XPAR_XINTC_USE_DCR" is not
> defined
> arch/ppc/syslib/xilinx_pic.c: In function 'ppc4xx_pic_init':
> arch/ppc/syslib/xilinx_pic.c:122: error: 'XPAR_INTC_0_BASEADDR' undeclared
> (first use in this function)
> arch/ppc/syslib/xilinx_pic.c:122: error: (Each undeclared identifier is
> reported only once
> arch/ppc/syslib/xilinx_pic.c:122: error: for each function it appears in.)
> arch/ppc/syslib/xilinx_pic.c:148: error: 'XPAR_INTC_0_KIND_OF_INTR' undeclared
> (first use in this function)
> make[1]: *** [arch/ppc/syslib/xilinx_pic.o] Error 1
> make: *** [arch/ppc/syslib] Error 2
>
> This to me looks like my xparameters.h file is missing something.. Any
> ideas?
Go into software settings, and set a driver for the intc core. (Or
you might be missing an interrupt controller entirely in your design)
BTW, I wouldn't bother with getting EDK to patch your kernel tree.
You're better off to generate the BSP into an empty directory and just
copy in your custom xparams file. The EDK patching is fragile if you
don't use exactly the right kernel version.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
prev parent reply other threads:[~2007-06-14 2:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 0:31 New to ML-310 biovore
2007-06-14 2:39 ` Grant Likely [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=fa686aa40706131939p75e168a8hfe626e5452261c1f@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=biovore@biovore.net \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).