[Dri-devel] Monday's DRI developer meeting reminder

2002-02-25 Thread Mike A. Harris
Just a reminder to everyone of the weekly DRI development meeting taking place on #dri-devel on irc.openprojects.net. The meetings start every Monday at 4:00pm EST (2100 UTC), although many developers show up early, so drop by early if you get a chance. There is also now an XFree86 general de

Re: [Dri-devel] DRI packages progress notice - what about specific options?

2002-02-25 Thread bcafarel
Quoting Jose Fonseca <[EMAIL PROTECTED]>: > Luckily, after sending the previous email the script completed > sucessfully. The generated packages are available at: > > http://mefriss1.swan.ac.uk/~jfonseca/dri/packages/ > > Unfortunately, as you can notice the packages are huge. Attached is a > f

Re: [Dri-devel] DRI packages progress notice - what about specific options?

2002-02-25 Thread José Fonseca
On 2002.02.25 10:02 [EMAIL PROTECTED] wrote: > ... > > Some good news, just when I'm away from school! (and its great connection > :) ). > But just a thought: it looks like you use the "standard" host.def for the > > mach64 build. And the last time I checked out the branch, the #define > MesaUse

Re: [Dri-devel] Compliance v. Performance (and mach64)

2002-02-25 Thread José Fonseca
On 2002.02.25 00:58 Leif Delgass wrote: > In investigating texture environment modes on the mach64, I've discovered > that the card can't modulate fragment and texture alpha values (this is > confirmed by the docs, experimentation, and comments in the utah-glx I've also been studying this but I'm

Re: [Dri-devel] latest trunk problems

2002-02-25 Thread Klaus Rose
After changing xc/xc/lib/GL/mesa/src/drv/mga/mga_xmesa.c line 227 from __driMesaMessage(...) to __driUtilMessage(...) it works for me. > Hi. I recently updated my version to the current tree (recently updated > to Mesa 4.0), and DRI no longer works. I'm using a 16MB G400, along with > kernel

Re: [Dri-devel] Compliance v. Performance (and mach64)

2002-02-25 Thread Leif Delgass
On Mon, 25 Feb 2002, José Fonseca wrote: > On 2002.02.25 00:58 Leif Delgass wrote: > > In investigating texture environment modes on the mach64, I've discovered > > that the card can't modulate fragment and texture alpha values (this is > > confirmed by the docs, experimentation, and comments in

Re: [Dri-devel] Compliance v. Performance (and mach64) (fwd)

2002-02-25 Thread Leif Delgass
> It doesn't explicitly state it in the docs, but it's not multiplying the > fragment alpha and texture alpha components. Instead, the texture alpha > value is used as the resulting alpha value of the texture application > (which can then be blended with the framebuffer depending on the blend >

Re: [Dri-devel] DRI packages progress notice - what about specific options?

2002-02-25 Thread Ian Romanick
On Mon, Feb 25, 2002 at 11:47:07AM +, José Fonseca wrote: > On 2002.02.25 10:02 [EMAIL PROTECTED] wrote: > > anyone is interested in athlon-compiled binary drivers, I can help (but > > not > > before march 4th). > > I think that there is no reason for not enabling every optimization in > Mes

Re: [Dri-devel] Compliance v. Performance (and mach64)

2002-02-25 Thread Ian Romanick
On Sun, Feb 24, 2002 at 07:58:14PM -0500, Leif Delgass wrote: > Given this hardware limitation, most GL_MODULATE cases can produce > incorrect results with alpha blending enabled. Using software fallbacks > for these cases could seriously impact performance in applications that > make heavy use

Re: [Dri-devel] DRI packages progress notice - what about specific options?

2002-02-25 Thread bcafarel
Quoting Ian Romanick <[EMAIL PROTECTED]>: > There are two parts to this. There is the assembly coded parts of Mesa > (for 3Dnow & SSE) and there are compile switches for GCC. For example, we may > wish to see if there are any benefits to building a version with > '-mcpu=i686' or '-mcpu=k6' or

Re: [Dri-devel] latest trunk problems

2002-02-25 Thread Keith Whitwell
Klaus Rose wrote: > > After changing xc/xc/lib/GL/mesa/src/drv/mga/mga_xmesa.c line 227 from >__driMesaMessage(...) to __driUtilMessage(...) it works for me. > Committed. Keith ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.

Re: [Dri-devel] Compliance v. Performance (and mach64)

2002-02-25 Thread Allen Akin
This is such a hard problem...there's no simple solution, and people have been thinking about it for over ten years. I'd advise against a configuration file that chooses conformance or performance on a feature-by-feature basis, for at least these reasons: Sometimes you need to choose con

[Dri-devel] IRC chat on now

2002-02-25 Thread Brian Paul
#dri-devel on irc.openprojects.net -Brian ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel

[Dri-devel] Re: More on TCL Testing...

2002-02-25 Thread Adam K Kirchhoff
On Mon, 25 Feb 2002, Keith Whitwell wrote: > > OK, great - it looks like some things work for you... That's an improvement, > anyway... > > What would be helpful would be to look at Mesa/samples, and identify what in > there works & doesn't work. Start with 'depth', 'prim', 'stars', 'tri'. >

Re: [Dri-devel] How to build DRI to use gprof see profile data

2002-02-25 Thread Michael
On Tue, Feb 05, 2002 at 04:12:35PM +0800, ³\¹ÅŠö wrote: > When I run glxgears, > it print out glx_init_prof, and glx_fini_prof. > But, how to produce gmon.out ?? Old message, but for completeness sake... export GLX_SO_MON=1 > I had tried to run xc/lib/GL/makeprofile.sh, > but print out so