At 19:19 26/05/2001 +0100, Steven Newbury wrote:
>On Saturday 26 May 2001 18:11, ralf willenbacher wrote:
>> Steven Newbury wrote:
>> > On Friday 25 May 2001 01:22, ralf willenbacher wrote:
>> It starts up fine but seems to only have a couple of Mb of
>>
>> > texture space available - while I h
On Saturday 26 May 2001 18:11, ralf willenbacher wrote:
> Steven Newbury wrote:
> > On Friday 25 May 2001 01:22, ralf willenbacher wrote:
> > > thanks for trying it out.
> > > i fixed a typo (again)..
> >
> >
> > In your patch you changed 'totalcard = b->size' and 'totalagp=b->size'
> > to 'tot
Steven Newbury wrote:
>
> On Friday 25 May 2001 01:22, ralf willenbacher wrote:
> > thanks for trying it out.
> > i fixed a typo (again)..
>
> In your patch you changed 'totalcard = b->size' and 'totalagp=b->size' to
> 'totalcard += b->size' and 'totalagp += b->size' in
> xc/lib/GL/mesa/src/d
On Friday 25 May 2001 01:22, ralf willenbacher wrote:
> thanks for trying it out.
> i fixed a typo (again)..
In your patch you changed 'totalcard = b->size' and 'totalagp=b->size' to
'totalcard += b->size' and 'totalagp += b->size' in
xc/lib/GL/mesa/src/drv/mga/mgatexmem.c. This change stop
"Peter Soetens (KaLTaN)" wrote:
> If other people experience similar successes with other mga cards, i think it
> would be cool if they (Gareth etc) made it part of the main branch.
with xf4.1 knocking on the door this would be a rather bad moment.
--
ralf willenbacher ([EMAIL PROTECTED])
On Thursday 24 May 2001 11:24, you wrote:
> >
> > I have been trying your patch against the current XFree86-CVS and it
> > seems to work quite well with my G400MAX. running quake2,Q3A and
> > xscreensaver hacks. Running at 1600x1200x32 with 32Mb allocated to
> > agpsize I did not encounter any in
thanks for trying it out.
i fixed a typo (again)..
--
ralf willenbacher ([EMAIL PROTECTED])
diff -u -r ./xc/lib/GL/mesa/src/drv/mga/mga_xmesa.c
./xc2/lib/GL/mesa/src/drv/mga/mga_xmesa.c
--- ./xc/lib/GL/mesa/src/drv/mga/mga_xmesa.cMon May 14 18:55:02 2001
+++ ./xc2/lib/GL/mesa/src/drv/mga/m
On Thursday 24 May 2001 04:59, Steven Newbury wrote:
> >Aaron Holtzman wrote:
> >> It would seem that Gareth Hughes ([EMAIL PROTECTED]) said:
> >> > At no time has the Matrox DRI driver used AGP memory for textures.
> >>
> >> Can you give us a quick outline of the work required to make this
> >> h
>Aaron Holtzman wrote:
>>
>> It would seem that Gareth Hughes ([EMAIL PROTECTED]) said:
>> > At no time has the Matrox DRI driver used AGP memory for textures.
>>
>> Can you give us a quick outline of the work required to make this
>> happen?
>>
>> cheers,
>> aaron
>>
>
>well.. i tried but cou
ralf willenbacher wrote:
>agptex.difType: Plain Text (text/plain)
+++ ./xc2/programs/Xserver/hw/xfree86/drivers/mga/mga_dri.c Mon May
14 21:04:37 2001
@@ -1190,6 +1225,14 @@
+ i = mylog2( pMGADRI->agpTextureSize / MGA_NR_TEX_REGIONS );
should be
+ i = mylog2( pMGADRIServer->agpT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(previously posted to the wrong list(dri-users) )
This is awesome !
pitty i can't take a look at it myself now, but i'll keep this patch for
further investigation...
did you take a look at the agp specs/demo posted on the developpers website
of m
Aaron Holtzman wrote:
>
> It would seem that Gareth Hughes ([EMAIL PROTECTED]) said:
> > At no time has the Matrox DRI driver used AGP memory for textures.
>
> Can you give us a quick outline of the work required to make this
> happen?
>
> cheers,
> aaron
>
well.. i tried but couldnt make it
It would seem that Gareth Hughes ([EMAIL PROTECTED]) said:
> At no time has the Matrox DRI driver used AGP memory for textures.
Can you give us a quick outline of the work required to make this
happen?
cheers,
aaron
___
Dri-devel mailing list
[EMAIL
On Tue, May 08, 2001 at 10:29:43PM -0400, Zilvinas Valinskas wrote:
> >
> > Of course, this being an open source project, and the G200/G400 specs
> > freely available, you could always work on it yourself :-)
> >
> > -- Gareth
> What about Radeon specs. ? Are they freely available ? ...
> *sigh
Zilvinas Valinskas wrote:
>
> >
> > Of course, this being an open source project, and the G200/G400 specs
> > freely available, you could always work on it yourself :-)
> >
> > -- Gareth
> What about Radeon specs. ? Are they freely available ? ...
> *sighs*.
No.
-- Gareth
>
> Of course, this being an open source project, and the G200/G400 specs
> freely available, you could always work on it yourself :-)
>
> -- Gareth
What about Radeon specs. ? Are they freely available ? ...
*sighs*.
>
> ___
> Dri-devel mailing list
Mike Westall wrote:
>
> > Of course, this being an open source project, and the G200/G400 specs
> > freely available, you could always work on it yourself :-)
>
> Exactly how does one go about obtaining the "freely available" specs.
> I have looked at the matrox web site and it was not obvious
> Of course, this being an open source project, and the G200/G400 specs
> freely available, you could always work on it yourself :-)
Exactly how does one go about obtaining the "freely available" specs.
I have looked at the matrox web site and it was not obvious to me but
maybe I missed somethin
Peter Soetens wrote:
>
> I reported this a while ago, and this still looks not fixed.
> When i'm running 1280*1024, my mgag200 memory is filled up with the
> backbuffer and depthbuffer leaving 0kb for textures.
>
> Why doesn't the driver use the reserved AGP memory ?
> my programs work but textu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I reported this a while ago, and this still looks not fixed.
When i'm running 1280*1024, my mgag200 memory is filled up with the
backbuffer and depthbuffer leaving 0kb for textures.
Why doesn't the driver use the reserved AGP memory ?
my progra
20 matches
Mail list logo
