From: Benjamin Herrenschmidt <bh40@calva.net>
To: Tom Rini <trini@kernel.crashing.org>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: whacked out 2.2.18preX - last gasp
Date: Tue, 21 Nov 2000 17:17:50 +0100 [thread overview]
Message-ID: <19341016094934.2031@192.168.1.2> (raw)
In-Reply-To: <20001121083623.H552@opus.bloom.county>
>
>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).
_2_5 will help configs with multiple PCI busses except for IO ports which
will still be available on the first bus only. This may get fixed for PCI
IO BARs if we end up mapping virtually all the IO spaces appended together.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-11-21 16:17 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
2000-11-21 16:17 ` Benjamin Herrenschmidt [this message]
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=19341016094934.2031@192.168.1.2 \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).