From: Kaoru Fukui <k_fukui@highway.ne.jp>
To: jronne@ics.uci.edu
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: two aty128 frame buffers?
Date: Tue, 5 Feb 2002 14:21:27 +0900 (JST) [thread overview]
Message-ID: <200202050524.OAA13555@mail.highway.ne.jp> (raw)
In-Reply-To: <20020204154626.C28199@reepicheep.ics.uci.edu>
On 4 Feb, Jeffery von Ronne wrote:
>
> Does anyone know how hard it would be to hack aty128fb to support a
> second Rage 128? Or am I better off trying to get the X server to talk
> directly to the second card?
>
> I have two PCI Rage 128's in my G4, which I'd like to use in a
> dual-headed Xinerama set up.
>
> So far I've only been able to get the X server (4.1.0 and 4.2.0) to
> work through framebuffer driven cards (X's ati/r128 drivers with aty128fb
> and X's fbdev with offb).
>
> When I've tried to tell X to talk directly to the unmanaged video card it
> complains about some unresolved drm symbols (they're different for 4.1
> and 4.2, for 4.1 its: "Symbol drmScatterGAtherAlooc from module
> /usr/X11R6/lib/modules/drivers/r128_drv.o"). I've tried with and without
> drm supporting kernels.
>
> Does anyone have any suggestions?
Add drm in Section Module
Section "Module"
Load "drm"
EndSection
Kaoru
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-05 5:21 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 [this message]
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
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=200202050524.OAA13555@mail.highway.ne.jp \
--to=k_fukui@highway.ne.jp \
--cc=jronne@ics.uci.edu \
--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).