From: Olaf Hering <olh@suse.de>
To: Matt Porter <mmporter@home.com>
Cc: Rudolf Ladyzhenskii <rudolf.ladyzhenskii@act-aus.net>,
"PPC-Linux list (E-mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 2.4.6 kernel on MCP750 board
Date: Tue, 24 Jul 2001 21:13:45 +0200 [thread overview]
Message-ID: <20010724211345.B20688@suse.de> (raw)
In-Reply-To: <20010719113849.A30665@cx258813-a.chnd1.az.home.com>; from mmporter@home.com on Thu, Jul 19, 2001 at 11:38:49AM -0700
On Thu, Jul 19, Matt Porter wrote:
>
> On Wed, Jul 18, 2001 at 09:54:41AM +1000, Rudolf Ladyzhenskii wrote:
> >
> > Hi, all
> >
> > I am trying to put the latest kernel on Motorola MCP750 card. 2.2 kernel
> > used to work fine, but 2.4.6 have some PCI problems.
> > It can not allocate resources to network interface and, as a result, I can
> > not boot.
> > Startup dump attached.
>
> The PCI subsystem is shooting itself in the foot when it sees a P2P
> bridge with I/O and Mem windows disabled. That's the case when you
> plug in a system master (that uses a transparent bridge to cPCI) in
> by itself. A peripheral card in any slot will avoid the issue.
>
> Apply the following patch (current linuxppc_2_4_devel / 2.4.7pre8) to
> cure the problem:
That fixed my mtx+, thanks :)
Changeset 1.152 in _2_4 broke it.
Gruss Olaf
--
$ man clone
BUGS
Main feature not yet implemented...
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-07-24 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 23:54 2.4.6 kernel on MCP750 board Rudolf Ladyzhenskii
2001-07-19 18:38 ` Matt Porter
2001-07-24 19:13 ` Olaf Hering [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-23 1:03 Rudolf Ladyzhenskii
2001-07-24 17:11 ` Matt Porter
2001-07-24 23:48 Rudolf Ladyzhenskii
2001-07-25 0:07 ` Matt Porter
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=20010724211345.B20688@suse.de \
--to=olh@suse.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mmporter@home.com \
--cc=rudolf.ladyzhenskii@act-aus.net \
/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).