From: "Timothy A. Seufert" <tas@mindspring.com>
To: Derrik Pates <dpates@dsdk12.net>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: two aty128 frame buffers?
Date: Thu, 7 Feb 2002 12:35:48 -0800 [thread overview]
Message-ID: <p05101400b888906c9a08@[10.0.0.42]> (raw)
In-Reply-To: <Pine.LNX.4.43.0202071127340.16392-100000@andromeda.dsdk12.net>
At 11:29 AM -0700 2/7/02, Derrik Pates wrote:
>On Wed, 6 Feb 2002, Ani Joshi wrote:
>
>> You can't use 2 cards which require ISA IO (vgaHW uses ISA IO on rage128)
>> right now, because of the multiple busses on the G4 machines. You can
>> comment out all the vgaHW calls and that will probably work, but without
>> doing that it will always crash on any ISA IO operation. The reason is
>> because your second bus's ISA IO isn't mapped.
>
>The issue is the same with the G3 tower - the video card is by default in
>the 32-bit, 66 MHz PCI slot, which is a logically separate bus from the
>64-bit, 33 MHz bus that the other 3 slots are part of.
Actually it's not the same issue. The blue&white G3 tower really has
just one logical PCI bus. The host bridge interfaces the processor
to the 66 MHz bus, and the 33 MHz bus is bridged to the 66 MHz bus
via a PCI-to-PCI bridge IC. I'm pretty sure ISA I/O is already
supposed to work for busses behind bridges.
The problem in the G4s is that Apple's Uni-N host bridge has three
logically distinct PCI busses which are peers rather than
subordinates. Each of them thinks it is PCI bus #0 -- the namespaces
are separate. The Linux kernel APIs for ISA I/O don't account for
the possibility of multiple PCI roots.
--
Tim Seufert
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-07 20:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 23:46 two aty128 frame buffers? Jeffery von Ronne
2002-02-05 5:21 ` Kaoru Fukui
2002-02-05 6:22 ` Jeffery von Ronne
2002-02-05 9:28 ` Michel Dänzer
2002-02-05 23:16 ` Jeffery von Ronne
2002-02-06 0:08 ` Michel Dänzer
2002-02-06 23:37 ` Jeffery von Ronne
2002-02-07 1:11 ` Michel Dänzer
2002-02-07 5:12 ` Ani Joshi
2002-02-07 18:29 ` Derrik Pates
2002-02-07 19:26 ` Ani Joshi
2002-02-07 22:35 ` Jeffery von Ronne
2002-02-07 20:35 ` Timothy A. Seufert [this message]
2002-02-07 19:55 ` Jeffery von Ronne
2002-02-08 1:15 ` Jeffery von Ronne
2002-02-08 1:34 ` Michel Dänzer
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='p05101400b888906c9a08@[10.0.0.42]' \
--to=tas@mindspring.com \
--cc=dpates@dsdk12.net \
--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).