Re: NetBSD on the Kurobox Pro

[KIYOHARA Takashi <kiyohara%kk.iij4u.or.jp@localhost>]

Hi! Donald,


From: Donald T Hayford <don%donhayford.com@localhost>
Date: Sat, 06 Sep 2008 12:45:36 -0400

> >>> ftp://ftp.netbsd.org/pub/NetBSD/misc/kiyohara/kuroboxarm
> >>>     
> >>
> >> Also newer sources:
> >>   ftp://ftp.netbsd.org/pub/NetBSD/misc/kiyohara/orion_nas
> >>
> >> And, I will upload the source of a newer version perhaps in a few 
> >> days.  ;-)

> > Got the files, thanks.  Should I build as big-endian (evbarm-eb) or 
> > little endian (evbarm-el)?

> Having recived no answer on the endianess of the processor yet, and 
> being the impatient type, I elected to go with little endian.  Is there 
> a way to tell?  The processor documentation says it supports both.

I always build it with evbarm.


> $ ./build.sh -O ../obj -T ../tools -m evbarm-el tools
> $ ./build.sh -O ../obj -T ../tools -U -u -m evbarm-el distribution
> $ ./build.sh -O ../obj -T ../tools -U -u -m evbarm-el kernel=ORION_NAS
> /home/hayford/net-k/src/sys/arch/evbarm/conf/ORION_NAS:193: `pci* at 
> orionpci?' is orphaned (nothing matching `orionpci?' found)
> *** Stop.
> 
> Looking in the ORION_NAS configuration file, I found:
> > # On-chip PCI Express Interface
> > orionpex0 at orion? addr 0xf1040000 irq 11
> > #orionpex1 at orion? addr 0xf1030000 irq 13    # 1182 and 1281 only
> >
> > # On-chip PCI Interface
> > #orionpci0 at orion? addr 0xf1030000 irq ?
> > # We do not know where to connect the interrupt of the PCI device. 
> > Therefore,
> > # interrupt will be establish to all pins.
> > #options     ORIONPCI_ESTABLISH_ALLGPPINTR
> >
> > # PCI bus support
> > options     PCI_NETBSD_CONFIGURE
> > #options     PCI_CONFIG_DUMP        # verbosely dump PCI config space
> >
> > pci*    at orionpex?
> > pci*    at orionpci?
> Not knowing any better, I removed the comment from
> > #orionpci0 at orion? addr 0xf1030000 irq ?

Oops... X-<
Sorry...


> and re-executed the last build.sh line ($ ./build.sh -O ../obj -T 
> ../tools -U -u -m evbarm-el kernel=ORION_NAS).
> Things appears to build ok, until it goes to link everything, at which 
> point I get the following error.

> #      link  ORION_NAS/netbsd
> /home/hayford/net-k/src/../tools/bin/arm--netbsdelf-ld -Map netbsd.map 
> --cref -T ldscript -X -o netbsd ${SYSTEM_OBJ} ${EXTRA_OBJ} vers.o
> ioconf.o:(.rodata+0x880): undefined reference to `orionpci_ca'
> 
> The following files were part of the link list, and all exist in 
> ..obj/sys/arch/ebvarm/compile/ORION_NAS
> orion_nas_machdep.o
> orion_intr.o
> orion_space.o
> orion_dma.o
> orion.o
> oriontmr.o
> orionpex.o
> orionpci.o
> orion_pci.o
> orion_mvsata.o
> if_oriongbe.o
> orion_ehci.o
> orion_twsi.o
> orion_com.o
> orion_a4x_space.o
> orion_a4x_io.o
> oriongpp.o
> 
> Grepping in src (grep -R "orionpci_ca" *) didn't find any files with the 
> missing reference (orionpci_ca), nor did "find" find any files named 
> ioconf* that seem to be associated with the orion/evbarm files.
> 
> So, I'm sort of stuck.  Any help is greatly appreciated.  Regards,
> Don

hmm..
I had seen the same error as you according to the memory before.  However,
the problem has been forgotten.  Can you wait until tomorrow?  I will
prepare my latest source. 

Thanks,
--
kiyohara