Re: two aty128 frame buffers?

On Wed, Feb 06, 2002 at 01:08:28AM +0100, Michel Dänzer wrote:

quoted

I tried applying your hack to a virgin XF 4.2.0 source tree, and
I get a signal 11 crash.  The last output shows the X server loading
vgahw.

I strated sprinkling the code with R128_TRACE messages, and as near as I can
tell, the vgaHWGetIOBase is crashing.

--
Jeffery von Ronne [off-list ref]
Graduate Student
Information and Computer Science
University of California, Irvine

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

On Don, 2002-02-07 at 00:37, Jeffery von Ronne wrote:

On Wed, Feb 06, 2002 at 01:08:28AM +0100, Michel Dänzer wrote:

quoted

quoted

I tried applying your hack to a virgin XF 4.2.0 source tree, and
I get a signal 11 crash.  The last output shows the X server loading
vgahw.

I strated sprinkling the code with R128_TRACE messages, and as near as I can
tell, the vgaHWGetIOBase is crashing.

Works here with a single chip... can you send me your XF86Config and X
server log privately?


--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

On Wed, 6 Feb 2002, Jeffery von Ronne wrote:

On Wed, Feb 06, 2002 at 01:08:28AM +0100, Michel Dänzer wrote:

quoted

quoted

I tried applying your hack to a virgin XF 4.2.0 source tree, and
I get a signal 11 crash.  The last output shows the X server loading
vgahw.

I strated sprinkling the code with R128_TRACE messages, and as near as I can
tell, the vgaHWGetIOBase is crashing.

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.


ani


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

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. What sort of mods
will it take to make that work, anyway?

I've discovered that putting both cards in bus 0 (64-bit, 33 MHz bus) gets
both the cards going, though - and well, that works for me...

Derrik Pates      |   Sysadmin, Douglas School   |    #linuxOS on EFnet
dpates@dsdk12.net |     District (dsdk12.net)    |    #linuxOS on OPN


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

On Thu, 7 Feb 2002, Derrik Pates wrote:

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. What sort of mods
will it take to make that work, anyway?

There is work now in X to get this working, it requires a layer of PCI
abstraction which is pretty raw at the moment.  Hopefully in a few months
something solid should come out.  However, since we're discussing Rage128
cards in Mac's here, it can be said that the vga IO that is being done is
totally unnecessary, as the Rage128 does not require a vga mode to be
saved or restored on Macs.  So totally disabling the vga IO if you are
just using those 2 cards on your machine can be a valid solution (for your
situation, obviously not an X solution).

I've discovered that putting both cards in bus 0 (64-bit, 33 MHz bus) gets
both the cards going, though - and well, that works for me...

Yes, unfortunately though people on AGP G4's tend to use an AGP and a PCI
card.  I suppose they could do what you are doing and use the bottom 2 (or
however it works on G4s) PCI cards if they have 2 PCI boards.


ani


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

At 11:29 AM -0700 2/7/02, Derrik Pates wrote:

On Wed, 6 Feb 2002, Ani Joshi wrote:

quoted

 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/