Any clues as to why when I access the PCI config 0 space (virt:0xf8000000,
real: 0x7b000000) the system locks up.

I'm on an ebsa285.

I access the config space as follows (I also hang in when scan_bus calls
pcibios_read_cfgbyte()). The following code is my attempt to isolate the
hang in pci_scanbus()

ulong   pci_cfg0_base = 0xf8000000;
ulong   *p2;
ulong   *p1;

for (i = 0; i < 16; i++)
{
         p1 = (ulong *)(pci_cfg0_base + (256 << i));
         printXX("pci %x %x \n", i, *p1);
}


Using a logic analyser I can see that address 0xc0007e00 is accessed and then
address 0x100 and the she's dead in the water.

0x7e00 is the translation entry for 0xf800000 to 0x7b000000. It looks good:

the translation table entry is:
                0xc0007e00: 0x7b000442    0xc0007e04: 0x7b100442 


--
Dave Baukus
        Inet Inc. - R & D
        [EMAIL PROTECTED]
        (972) 578 - 3930
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]

Reply via email to