Walnut PCI bridge can't be detected

[Jacky Lam]

    Forget to attach my boot log. I have turned on all PCI debug message and
added some printk to trace the flow of kernel. Beside that, I don't have any
change related.

----- Original Message -----
From: "Jacky Lam" <jackylam at astri.org>
To: <linuxppc-embedded at lists.linuxppc.org>
Sent: Monday, October 13, 2003 10:38 AM
Subject: Walnut PCI bridge can't be detected


>
> Dear all,
>
>     Concerning my pervious posts about the problem on receiving interrupt
> from PCI cards. I guess it is the problem of PCI bridge..(at least I think
> it is related). Watching the old post in this list, someone post the boot
> log of Walnut board here long time ago. The boot log contians a line to
> detect PCI bridge just after the line"PCI: Probing PCI hardware". However,
> the current devel tree running on Walnut doesn't have this.
>
>     Also, under /proc/bus/pci and /proc/pci, I can't see any information
> about the brdige.
>
>     Moreover, I find that there is a minor different on a bit in my ES1371
> card on Walnut from that on PC. On PC, ES1371 seems will capture an "Slave
> interrupt controller" event just after bootup. But on Walnut, the event
will
> become "Slave DMA controller".
>
>     I think these all differents are rooted from some miss configuration
> about PCI in u-boot or kernel early  initialization. I am not familiar
with
> PCI. Hope someone here knows what is happening and gives me some idea on
how
> to fix that.
>
>     Thanks so much.
>
> Best regards,
> Jacky
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: minicom.cap
Type: application/octet-stream
Size: 9949 bytes
Desc: not available
Url : http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20031013/91d070d3/attachment.obj