linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* New to ML-310
@ 2007-06-14  0:31 biovore
  2007-06-14  2:39 ` Grant Likely
  0 siblings, 1 reply; 2+ messages in thread
From: biovore @ 2007-06-14  0:31 UTC (permalink / raw)
  To: linuxppc-dev

Hello everyone on the list,
	I have managed to get my hands on a ML-310 play around with in my spare time 
at home.  I working on trying to build a linux kernel for the system.  I have 
ISE 9.1i and EDK 9.1i and am using there system generator to patch a 
linux-2.6.22-rc3 kernel I checked out of the montivista kernel git repos.   I 
am familiar with crosscompiling kernels for fix processors of arm and ppc, 
but I am running into problems dealing with the PPC405 in the virtex-II.
The EDK generates a bunch of code and patches the kernel.  I then go into the 
kernel directory and run ./xmake and it seems to go off and do some stuff to 
the .config file and then starts to build the kernel.  I all goes nicely 
until it hits the following error.

  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?

Peter Fetterer
--
The force is like duct tape.  It has a dark side, a light side and binds the 
universe together.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: New to ML-310
  2007-06-14  0:31 New to ML-310 biovore
@ 2007-06-14  2:39 ` Grant Likely
  0 siblings, 0 replies; 2+ messages in thread
From: Grant Likely @ 2007-06-14  2:39 UTC (permalink / raw)
  To: biovore; +Cc: linuxppc-dev

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-06-14  2:39 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-06-14  0:31 New to ML-310 biovore
2007-06-14  2:39 ` Grant Likely

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).