From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <mlan@cpu.lu>, <dan_bethe@yahoo.com>
Cc: <nicoya@apia.dhs.org>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 9600 maturity?
Date: Mon, 15 Apr 2002 10:19:58 +0100 [thread overview]
Message-ID: <20020415091958.19056@smtp.wanadoo.fr> (raw)
In-Reply-To: <E16xBvj-000073-00@piglet.grunz.lu>
>No, 2.4 kernels should have solid PCI even in the presence of multiple
>host bridges (which was the problem on the dual-bandit 9x00). The only
>potentially remaining problem could be access to IO space on the second
>bus. Ben, can you comment?
I can't. I would love having someone try this in details and tell me ;)
I suspect the second bandit can only produce "high" IO addresses (thus
precenting use of legacy stuff).
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-15 9:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 7:43 9600 maturity? Dan Bethe
2002-04-15 8:26 ` Tony 'Nicoya' Mantler
2002-04-15 10:41 ` Dan Bethe
2002-04-15 17:32 ` Tony 'Nicoya' Mantler
2002-04-15 19:03 ` ATI 7000 and dual-monitor X? (was Re: 9600 maturity?) Stefan Jeglinski
2002-04-15 19:27 ` Ani Joshi
2002-04-15 22:25 ` Tony 'Nicoya' Mantler
2002-04-16 8:01 ` Olaf Hering
2002-04-16 22:03 ` Michel Lanners
2002-04-17 6:37 ` Geert Uytterhoeven
2002-04-17 7:04 ` Ani Joshi
2002-04-17 18:53 ` Michel Lanners
2002-04-17 5:35 ` Ani Joshi
2002-04-17 1:57 ` benh
2002-04-22 15:22 ` Olaf Hering
2002-04-15 19:14 ` 9600 maturity? Michel Lanners
2002-04-15 9:19 ` Benjamin Herrenschmidt [this message]
2002-04-16 5:59 ` Michel Lanners
2002-04-16 0:54 ` benh
2002-04-15 21:30 ` Jeff Walther
2002-04-15 13:38 ` Jeff Walther
2002-04-15 5:01 ` benh
2002-04-15 16:48 ` PPB Bug in PowerSurge: was: 9600 maturity Jeff Walther
2002-04-15 7:57 ` benh
2002-04-15 19:01 ` Jeff Walther
2002-04-15 9:29 ` Benjamin Herrenschmidt
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=20020415091958.19056@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=dan_bethe@yahoo.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
--cc=nicoya@apia.dhs.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).