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 file list

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 MesaUse3DNow YES

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 the

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 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 ... in

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]

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

[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 some error