From: "Jacky Lam" <jackylam@astri.org>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Walnut PCI bridge can't be detected
Date: Mon, 13 Oct 2003 10:38:46 +0800 [thread overview]
Message-ID: <001d01c39133$20f088a0$2803050a@JackyLam> (raw)
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
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-10-13 2:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 2:38 Jacky Lam [this message]
2003-10-13 3:05 ` Walnut PCI bridge can't be detected Jacky Lam
2003-10-13 3:50 ` Eugene Surovegin
2003-10-13 6:33 ` Jacky Lam
2003-10-13 7:03 ` Eugene Surovegin
2003-10-13 7:13 ` Jacky Lam
2003-10-14 4:27 ` Xiaoshan Zuo
2003-10-14 5:41 ` Eugene Surovegin
2003-10-14 7:27 ` Xiaoshan Zuo
2003-10-14 5:51 ` Jacky Lam
2003-10-15 17:36 ` Xiaoshan Zuo
2003-10-16 1:07 ` Jacky Lam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001d01c39133$20f088a0$2803050a@JackyLam' \
--to=jackylam@astri.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).