> It's either that, or the person who sent Linus the patch should submit
> it here. I think the latter is far more difficult.
>
> Otherwise we (as in someone on the DRI lists - not necessarily a committer to
> the project) are going to have to track the 2.5.x series and 2.4.x series
> for stable a
FYI, for those looking for a Savage based board to use in developing
a driver--assuming you're not motivated by having one already--I
noticed this at computer geeks:
Savage IX based:
http://www.compgeeks.com/details.asp?invtid=ASVGB1-8M
Savage4LT based:
http://www.compgeeks.com/details.asp?invtid
Oh, now that's even more annoying than SPAM usually is!
Here I was thinking that someone was going to announce that NVidia
decided to support open source or that the texture compression pattent
was going to be opened to the DRI group or *something* cool.
*sigh*
Cheers,
David
> Ehm. Are you disabling 2D accel in XF86Config (see the readme about it)?
No, but I'm hanging my head in shame because I ever read the post where
you talked about using the same 2D/3D locking trick as the mach64 driver.
I'll go read now...
Cheers,
David
--
> On Mon, 2002-07-08 at 06:51, David Willmore wrote:
>
> > In X server startup, the drm fails to load. If I exit and try to modprobe
> > it myself, I get errors about a bunch of AGP symbols not being resolved
>
> Try recompiling the module with (in s3v.h)
>
&g
I just did an informal real world benchmark on the Mach64
driver 20020704. Bzflag runs fine without any texturing,
but with all other options except smoothing. That one
knocked performance down horribly, too. In relatively
simple worlds with all but the two mentioned settings at
max, I was get
Well, I've been waiting what seems like forever for a driver
for my laptop and now there is one! What a happy day! One
problem, it's an older Compaq laptop and uses a propriatary
chipset (and AGP bridge) so no AGPGART. *do-oh*
Noone happens to have a AGPGART for it hiding somewhere, do
they?
I had a lockup on an older version of the mach64 DRI driver, so
I thought I'd retest with a newer one. gltestperf locks up (no
response to keyboard, but mouse still moves--it locked up as well
in the older version) on the ZSmooth Triangles size:480 test.
Not immediately, but it locks up after
> On Tue, Jul 02, 2002 at 10:48:29PM +0100, Tim Smith wrote:
> >
> > Great. So we're OK on
> >
> > Radeon 7500
> > Radeon 7200
> >
> > anyone got a Radeon 7000 or old Radeon no-number to try it on?
>
> 7200 is the "old Radeon no-number" AFAIK ;)
This brings up something that I've been meaning
So, I downloaded the newest mach64 code and installed it.
After fighting with the drm not loading automatically,
and the bit depth being too high *smack*, I got direct
rendering working! :) ~250 fps on glxgears is spiffy--
beats ~60 without DRI.
With that behind me, I decided to get brave. So,
> Keith Whitwell wrote:
> OK, maybe I'm getting carried away.
>
> But as I see it, there aren't many people in total on dri_devel+dri_users.
> The only people who can really answer dri_users questions are on dri_devel
> anyway. Why have two lists?
>
> There aren't a great number of dri_users
11 matches
Mail list logo
