From: Tom Rini <trini@kernel.crashing.org>
To: Rajappa Iyer <rsi@panix.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: P2P bridge (DEC 21154) initialization on MCP750
Date: Tue, 28 May 2002 11:43:32 -0700 [thread overview]
Message-ID: <20020528184332.GK1295@opus.bloom.county> (raw)
In-Reply-To: <200205281835.g4SIZKf09966@panix3.panix.com>
On Tue, May 28, 2002 at 02:35:20PM -0400, Rajappa Iyer wrote:
>
> Matt Porter <porter@cox.net> writes:
>
> > On Mon, May 27, 2002 at 06:14:24PM -0400, Rajappa Iyer wrote:
>
> > > 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.
>
> > 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.
>
> Sure, here it is.
>
> What I mean by unbearably slow is that once init starts running, the
> system just slows down to a complete crawl. It takes about 2 minutes
> for the login prompt to appear. To run lspci -v took about 10 minutes
> (I'm not exaggerating.)
Oh, yes. The OpenPIC_InitSenses needs to be updated. Look at
arch/ppc/platforms/lopec_setup.c
Patches appreciated.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-05-28 18:43 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
2002-05-28 18:35 ` Rajappa Iyer
2002-05-28 18:43 ` Tom Rini [this message]
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=20020528184332.GK1295@opus.bloom.county \
--to=trini@kernel.crashing.org \
--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).