I dunno, AFR could be done. Assuming the regular rage128 driver can work on
the Fury MAXX, you're halfway there (well, not quite, but anyway). Once you
can find the 2nd (slave) chip's memory map off the AGP bus (I assume there's
also a bridge chip involved since AGP
can only take one video devic
Since we ship a separate Mesa library for back-compatibility with
XFree86 3.3.6, we do not need XFree86 building the libGL, and
friends and I would like to disable it, but can't find any
relevant Imake directives.
In the past we have worked around this by doing the following in
our specfile:
{
Thanks for all the work Gareth, comments, help, emails, etc !! Wish you
the best of luck.
PS. hope they gave you a visa to make it to the states without sweat :)
Free, encrypted, secure Web-based email at www.hushmail.com
On Sun, Jun 03, 2001 at 10:00:45AM +, Bobakitoo wrote:
> hi,
> Where do i get linux drm v3.0.?
> dri as in xfree4.1.0 dont like drm in linux 2.4.5.
> Is it the lates kernel... how can you all work on code
> not yet aviable(until is somme where else)
>
> "[dri] mga.o kernel module versio
I spent a while this weekend looking in to this; it seems that the
problem is related to some AGP writes either writing corrupt data or
otherwise causing an instability. The bad mode problem seems to be
one symptom of this -- the modeline registers are probably receiving
corrupt data. I added s
AFR may or may not be workable, but all Kyro work is being done in house (a
la Nvidia) by STmicro. They're expecting a Kyro/Kyro2 closed source driver
for XFree4.X to be ready any decade now.
Rich 'Forge' Mingin
Open Source Advocate
Quake 3 Junkie
Aspiring Tribes 2 Junkie
- Original Message
