From: "Jacky Lam" <jackylam@astri.org>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Walnut PCI bridge can't be detected
Date: Mon, 13 Oct 2003 14:33:51 +0800 [thread overview]
Message-ID: <002801c39153$f76fd3c0$2803050a@JackyLam> (raw)
In-Reply-To: 5.1.0.14.2.20031012203903.02e546d8@mail.ebshome.net
> Also, according to the log you posted bus enumeration was successful and
> your device (es1371) was found. So I don't think you have a problem with a
> bridge.
>
> FYI, bridge is not responsible for delivering IRQs from your card. IRQ
> lines from the PCI slots are directly wired to the UIC (see
> walnut::ppc405_map_irq for actual mapping).
Yes, I know. Let me clarify my question again...Sorry for my blur
question.
What I mean is:
Will there some miss configuration of bridge which will affect the
behavior of PCI cards/slots?
>
> According to your log you have inserted card into the PCI slot 1, is this
> correct ?
>
> If you still suspect that you have bridge problem, just insert some other
> PCI card which is know to be supported by PPC kernel and see...
Yes. Is there a list of popular PCI cards which are supported by PPC
kernel directly without need of any modifications?
Thanks.
Regards,
Jacky
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-13 6:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 2:38 Walnut PCI bridge can't be detected Jacky Lam
2003-10-13 3:05 ` Jacky Lam
2003-10-13 3:50 ` Eugene Surovegin
2003-10-13 6:33 ` Jacky Lam [this message]
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='002801c39153$f76fd3c0$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).