From: Ani Joshi <ajoshi@shell.unixbox.com>
To: Jeffery von Ronne <jronne@ics.uci.edu>
Cc: "Michel Dänzer" <michel@daenzer.net>,
"Kaoru Fukui" <k_fukui@highway.ne.jp>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: two aty128 frame buffers?
Date: Wed, 6 Feb 2002 21:12:22 -0800 (PST) [thread overview]
Message-ID: <Pine.BSF.4.44.0202062110280.82577-100000@shell.unixbox.com> (raw)
In-Reply-To: <20020206153744.E3189@reepicheep.ics.uci.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 811 bytes --]
On Wed, 6 Feb 2002, Jeffery von Ronne wrote:
>
> On Wed, Feb 06, 2002 at 01:08:28AM +0100, Michel Dänzer wrote:
> > > 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/
next prev parent reply other threads:[~2002-02-07 5:12 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 [this message]
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
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=Pine.BSF.4.44.0202062110280.82577-100000@shell.unixbox.com \
--to=ajoshi@shell.unixbox.com \
--cc=jronne@ics.uci.edu \
--cc=k_fukui@highway.ne.jp \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michel@daenzer.net \
/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).