From: Tom Rini <trini@kernel.crashing.org>
To: Stefan Jeglinski <jeglin@4pi.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: whacked out 2.2.18preX - last gasp
Date: Tue, 21 Nov 2000 08:36:23 -0700 [thread overview]
Message-ID: <20001121083623.H552@opus.bloom.county> (raw)
In-Reply-To: <p04330103b64042f6fa28@[206.6.156.5]>; from jeglin@4pi.com on Tue, Nov 21, 2000 at 10:25:45AM -0500
On Tue, Nov 21, 2000 at 10:25:45AM -0500, Stefan Jeglinski wrote:
> > > It's frankly hard at this point to buy that one of my PCI devices is
> >> walking over the kernel. Or if it is, it looks like the end of the
> >> Linux line for my PowerTowerPro with the 2940 card. I think this is
> >> either a bug in the aic7xxx driver that has been exposed by 2.2.18
> >> changes (highly doubtful, there are too many 2940s out there for it
> >> to have been missed), or a linux-pmac bug. I just don't know enough
> >> yet to prove it, much less find it.
> >
> >Hmm. 2.2.18pre21 from linuxppc_2_2 bk works on my G4/Yikes! with a 2940UW
> >in it. What compiler are you using?
>
> dmesg:
>
> gcc version 2.95.2 19991024 (release/franzo) #1
>
> rpm -qa |grep gcc:
>
> gcc-2.95.2-1i
> gcc-c++-2.95.2-1i
> gcc-objc-2.95.2-1i
You might wanna try 2.95.3-2j, which should be in fsirl's dir on dev. But I
really do doubt this is why.
> What I'm worried about mainly is the 6 slots and the PCI bridge
> structure in the PowerTowerPro (akin to PowerMac 9500). It is more
> "complex" than G4, no? From my previous discussion with you and
> others, I gather that there are a lot of problems with the PCI stuff,
> that may not be cleared up for quite a while?
Actually, the linuxppc_2_5 bitkeeper tree (which is getting merged into
2_3, for inclusing into hopefully 2.4.0-final from linus) has a giant PCI
re-write, so 9500s/et al might actually work happily now. But yes, from what
I've gathered from trying to work w/ a 9500 and 2.2.18pre21 there just might
be something broken now. (The video card refuses to work at all, regardless
of slot).
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-11-21 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 4:03 whacked out 2.2.18preX - last gasp Stefan Jeglinski
2000-11-21 9:50 ` Michael Schmitz
2000-11-21 15:10 ` Tom Rini
2000-11-21 15:25 ` Stefan Jeglinski
2000-11-21 15:36 ` Tom Rini [this message]
2000-11-21 16:17 ` Benjamin Herrenschmidt
2000-11-21 21:48 ` Michel Lanners
2000-11-21 22:17 ` Stefan Jeglinski
[not found] <Pine.LNX.4.10.10011211049130.22058-100000@opal.biophys.uni-duesseldorf.de >
2000-11-21 14:03 ` Stefan Jeglinski
2000-11-21 14:29 ` Michael Schmitz
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=20001121083623.H552@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=jeglin@4pi.com \
--cc=linuxppc-dev@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).