From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Steven Hanley <sjh@wibble.net>,
Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: agpgart? or how to use dri?
Date: Fri, 2 Feb 2001 01:02:03 +0100 [thread overview]
Message-ID: <19341227173347.15692@mailhost.mipsys.com> (raw)
In-Reply-To: <20010202095306.A7859@chiru.svana.org>
>
>> I slightly hacked my own
>> to build since I lack the glide libs necessary for the 3dfx stuff to
>compile.
>
>what does glide have to do with this? isnt that only used with tdfx?
Yes, but the Makefile of the kernel DRM modules will build all modules
(3dfc, ati, ...) and so would fail when the glide headers are not there.
>So where do I find out about pci gart and how to make the r128 driver
>compile using it? Should I simply read through the Makefil and the r128 code
>and ifnd the stuff related to pci gart and enable anything there possibly
>turned off or some such?
Well, what I did was to:
- Get Gareth CVS branch
- Make World
- remove tdfx in the drivers Makefile and the DRM kernel makefile
- Re-make
- Make DRM modules (make -f Makefile.linux in the DRM kernel directory)
- make install
Note that for a Pismo (rage M3), you'll also need to edit your XF86Config
and do
- Disable "UseFBDev" option as the current aty128fb does work correctly
in 16 bits
- Set Option "ProgramFPRegs" "No" or the driver will crash
- Set your bit depth to 16 bits (not 15 nor 32)
Also, using windowed GL apps tend to hang the server as soon as a 2D
operation is done. This problem seem to be specific to the RageM3 of the
Pismo.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-02 0:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 7:48 agpgart? or how to use dri? Steven Hanley
2001-02-01 11:29 ` Benjamin Herrenschmidt
2001-02-01 22:53 ` Steven Hanley
2001-02-01 23:25 ` Michel Dänzer
2001-02-02 0:02 ` Benjamin Herrenschmidt [this message]
2001-02-02 15:27 ` Kostas Gewrgiou
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=19341227173347.15692@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sjh@wibble.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).