Skip to contentSkip to conversation

PCI support on the ML310 (Linux 2.4/2.6)

DISCUSSION Juliana Su 1 participant 1 message Aug 4, 2008

lore
Share & tools
lore

Juliana Su

author
#0 lore raw

Hi,

I am trying to get PCI support on the ML310. I was able to port Linux 2.6 (linux-2.6-virtex from Secret Lab) onto the board, but unfortunately there is no PCI support in the kernel. When I enabled PCI support, I got the same errors (see below) that were reported on the Secret Lab Wiki.

CC arch/ppc/syslib/ppc4xx_setup.o
arch/ppc/syslib/ppc4xx_setup.c: In function `ppc4xx_map_io':
arch/ppc/syslib/ppc4xx_setup.c:118: error: `PPC4xx_PCI_IO_VADDR' undeclared (first use in this function) arch/ppc/syslib/ppc4xx_setup.c:118: error: (Each undeclared identifier is reported only once arch/ppc/syslib/ppc4xx_setup.c:118: error: for each function it appears in.) arch/ppc/syslib/ppc4xx_setup.c:119: error: PPC4xx_PCI_IO_PADDR' undeclared (first use in this function) arch/ppc/syslib/ppc4xx_setup.c:119: error: PPC4xx_PCI_IO_SIZE' undeclared (first use in this function) arch/ppc/syslib/ppc4xx_setup.c:120: error: PPC4xx_PCI_CFG_VADDR' undeclared (first use in this function) arch/ppc/syslib/ppc4xx_setup.c:121: error: PPC4xx_PCI_CFG_PADDR' undeclared (first use in this function) arch/ppc/syslib/ppc4xx_setup.c:121: error: PPC4xx_PCI_CFG_SIZE' undeclared (first use in this function) arch/ppc/syslib/ppc4xx_setup.c:122: error: PPC4xx_PCI_LCFG_VADDR' undeclared (first use in this function) arch/ppc/syslib/ppc4xx_setup.c:123: error: PPC4xx_PCI_LCFG_PADDR' undeclared (first use in this function) arch/ppc/syslib/ppc4xx_setup.c:123: error: PPC4xx_PCI_LCFG_SIZE' undeclared (first use in this function) make[1]: *** [arch/ppc/syslib/ppc4xx_setup.o] Error 1
make: *** [arch/ppc/syslib] Error 2

I went back to Linux 2.4 (v2.4.20_mvl31-ml300), but the system hangs during ml310_init( ), specifically when it gets to pci_init( ), in ml310.c. I put some print statements in ml310.c to debug and found out that it gets pass the first two lines in pci_init( ) before hanging. Basically, all I get on my screen is:

Xilinx ML310 Board-Specific Initialization:

ml310_init( ) looks like this:

void
ml310_init()
{
prints("\n\n");
prints("Xilinx ML310 Board-Specific Initialization:\n"); prints("\n");

pci_init();
ppb_init(9);
pci_scan();
sio_init();
sbr_init();
};

and pci_init( ) looks like this:

void
pci_init()
{
/* self-configuration */ WR32(PCI_CONFIG_ADDR, htole32(0x80004004)); // address WR32(PCI_CONFIG_DATA, htole32(0xffff0147)); // data /* max latency timer on bridge */ WR32(PCI_CONFIG_ADDR, htole32(0x8000400c)); // address WR32(PCI_CONFIG_DATA, htole32(0x0000ff00)); // data /* max bus number */
WR32(PCI_CONFIG_ADDR+8, htole32(0xff000000));
};

ml310.c was generated when I made the BSP in Xilinx EDK 9.1. I copied it, along with the other files from the BSP, into the kernel source. I am using a Crosstool cross-compiler, gcc-3.4.1-glibc-2.3.3. I have also tried the linuxppc-2.4 and mvistappc_2_4_devel kernels from source.mvista.com, but those both crashed with similar (and several) errors concerning ide-taskfile.c during compilation.

Is anybody aware of how to manually map the PCI constants in 2.6 and willing to help me map them? Does anybody have an idea why pci_init( ) is getting stuck? Any suggestions, in general, would be greatly appreciated.

Let me know if I need to provide more information or code. Thanks!

-Juliana