On Thu, Feb 01, 2001 at 12:29:39PM +0100, Benjamin Herrenschmidt wrote:
The current agpgart driver won't work on PPC, the Apple AGP host bridge
is not supported.
so I guessed
The new DRI support announced by Gareth is using the PCI GART which
doesn't need the AGP capabilities.
makes sense
Don't enable either AGP or DRI in your
kernel, and build the kernel r128 DRM module from XFree sources.
I didnt, but as mentioned when I dont have AGP gart enabled in the kernel
make in the kernel module directory in the X Free source tree only makes
tdfx, it fdoesnt do r128 or anything else.
You need
to use the CVS branch posted earlier by Gareth.
I am using that branch.
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?
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?
See You
Steve
--
sjh@wibble.net http://wibble.net/~sjh
Look Up In The Sky
Is it a bird? No
Is it a plane No
Is it a small blue banana?
Yes
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Steven Hanley wrote:
quoted
Don't enable either AGP or DRI in your
kernel, and build the kernel r128 DRM module from XFree sources.
I didnt, but as mentioned when I dont have AGP gart enabled in the kernel
make in the kernel module directory in the X Free source tree only makes
tdfx, it fdoesnt do r128 or anything else.
Have you tried make -f Makefile.linux ? And are you sure that it is picking up
the right kernel headers?
quoted
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?
Exactly, that's why you have to disable it in host.def or you get errors
during the build.
Michel
--
Earthling Michel Dänzer (MrCooper) \ Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast \ XFree86 and DRI project member
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
quoted
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/
On Fri, 2 Feb 2001, Benjamin Herrenschmidt wrote:
quoted
quoted
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.
.....
Well, what I did was to:
- Get Gareth CVS branch
- Make World
- remove tdfx in the drivers Makefile and the DRM kernel makefile
Until now the default for ppc was #define HasGlide3 NO if this has been
changed to YES, then disabling it in you hosts.cf should work.
Kostas
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/