From: Matt Porter <porter@cox.net>
To: Rajappa Iyer <rsi@panix.com>
Cc: Matt Porter <porter@cox.net>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: P2P bridge (DEC 21154) initialization on MCP750
Date: Mon, 27 May 2002 16:46:26 -0700 [thread overview]
Message-ID: <20020527164626.A1740@home.com> (raw)
In-Reply-To: <200205272214.g4RMEOP02787@panix3.panix.com>; from rsi@panix.com on Mon, May 27, 2002 at 06:14:24PM -0400
On Mon, May 27, 2002 at 06:14:24PM -0400, Rajappa Iyer wrote:
> Matt Porter <porter@cox.net> writes:
>
> > On Fri, May 24, 2002 at 09:14:21PM -0400, Rajappa Iyer wrote:
> > >
> > > I'm having problems with the PCI-PCI bridge (DEC 21154) on the MCP750
> > > and would appreciate any words of wisdom. Basically, this bridge does
> > > not get initialized and therefore no devices are probed on the
> > > secondary bus.
>
> > Use _devel and start with the pplus port. 'make pplus_config'
>
> Thanks. This did improve the situation somewhat in that the P2P
> bridge is now initialized properly, but the devices beyond it are
> still not probed. Incidentally, I had to work with 2.5.x, since the
> 2.4 devel kernel was, for some reason, unbearably slow.
>
> Here's the dmesg. Does it set off any alarm bells?
You're the first person to try one of these boards on 2.5 that I've
heard of. Can you explain what you mean by "unbearably slow" on
_devel? Please enable DEBUG in arch/ppc/kernel/pci.c and
drivers/pci/pci.c and repost those kernel messages.
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-27 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-25 1:14 P2P bridge (DEC 21154) initialization on MCP750 Rajappa Iyer
2002-05-25 3:09 ` Matt Porter
2002-05-27 22:14 ` Rajappa Iyer
2002-05-27 23:46 ` Matt Porter [this message]
2002-05-28 18:35 ` Rajappa Iyer
2002-05-28 18:43 ` Tom Rini
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=20020527164626.A1740@home.com \
--to=porter@cox.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rsi@panix.com \
/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).