Re: R300 DRI report

2005-07-13 Thread Aapo Tahkola
On Wed, 13 Jul 2005 17:22:36 +0300 Aapo Tahkola <[EMAIL PROTECTED]> wrote: > Also, r300s state management is not currently very "efficient" as can be seen > from oprofiled reports... :) Measured this and state traffic seems to go from 10 to 60 MB per second depending on application. Tnl program

getting r300 into Mesa

2005-07-13 Thread Shawn Starr
Do we have a plan on doing this? It would be good to merge things since you don't want to diverge too much? Shawn. --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to e

Re: Mesa strict aliasing probs fixed

2005-07-13 Thread Brian Paul
Matthias Hopf wrote: On Jul 13, 05 09:16:32 -0600, Brian Paul wrote: find a patch attached that fixes all remaining strict-aliasing problems when compiling Mesa with gcc 4 (at least for me). Are you sure you've got the #ifdef logic correct? I just copied the one that was already present an

Re: Mesa strict aliasing probs fixed

2005-07-13 Thread Matthias Hopf
On Jul 13, 05 09:16:32 -0600, Brian Paul wrote: > >find a patch attached that fixes all remaining strict-aliasing problems > >when compiling Mesa with gcc 4 (at least for me). > > Are you sure you've got the #ifdef logic correct? I just copied the one that was already present and didn't think muc

Re: Mesa strict aliasing probs fixed

2005-07-13 Thread Brian Paul
Matthias Hopf wrote: Hi, find a patch attached that fixes all remaining strict-aliasing problems when compiling Mesa with gcc 4 (at least for me). Are you sure you've got the #ifdef logic correct? #if defined(GLX_VERSION_1_1) && defined(GLX_SGIX_fbconfig) typedef void *fbc_t; #else typedef GL

Mesa strict aliasing probs fixed

2005-07-13 Thread Matthias Hopf
Hi, find a patch attached that fixes all remaining strict-aliasing problems when compiling Mesa with gcc 4 (at least for me). CU all Matthias -- Matthias Hopf <[EMAIL PROTECTED]>, SuSE labs, Zimmer 3.2.06, Tel. 74053-715 Index: src/glut/glx/glut_dstr.c ==

Re: R300 DRI report

2005-07-13 Thread Aapo Tahkola
On Wed, 13 Jul 2005 13:27:31 +0200 Lorenzo Colitti <[EMAIL PROTECTED]> wrote: > Aapo Tahkola wrote: > >>atlantis -root -whalespeed 458 -delay 0 -size 8350 -count 3 -gradient -fps > >> > >>Changed this for atlantis and it gave me 23fps instead of 3, thanks. > > > > I get 120 fps with color tiling

Re: Mesa build problems on non-i386 platform.

2005-07-13 Thread Keith Whitwell
Oops. Sorry about this. I've committed an equivalent change. Keith Egbert Eich wrote: I needed the patch below to build Mesa CVS head on x86-64. Otherwise gcc complained about RESTORE_FPU being undefined when compiling t_vb_arbprogram.c Egbert. diff -u -r1.4 t_vb_arbprogram.h --- src/mes

Mesa build problems on non-i386 platform.

2005-07-13 Thread Egbert Eich
I needed the patch below to build Mesa CVS head on x86-64. Otherwise gcc complained about RESTORE_FPU being undefined when compiling t_vb_arbprogram.c Egbert. diff -u -r1.4 t_vb_arbprogram.h --- src/mesa/tnl/t_vb_arbprogram.h 10 Jul 2005 11:23:10 - 1.4 +++ src/mesa/tnl/t_vb_arbpr

Re: R300 DRI report

2005-07-13 Thread Lorenzo Colitti
Aapo Tahkola wrote: atlantis -root -whalespeed 458 -delay 0 -size 8350 -count 3 -gradient -fps Changed this for atlantis and it gave me 23fps instead of 3, thanks. I get 120 fps with color tiling on pretty much same hw as you and 1280x1024 resolution. Youll need to use xorg cvs and ColorTilin

Re: R300 DRI report

2005-07-13 Thread Aapo Tahkola
On Tue, 12 Jul 2005 21:33:16 +0200 Sander Sweers <[EMAIL PROTECTED]> wrote: > On 12/07/05, Michel Dänzer <[EMAIL PROTECTED]> wrote: > > On Tue, 2005-07-12 at 13:06 +0200, Sander Sweers wrote: > > > > > > Well xscreensaver is horrible to do any tests with, I never get above > > > the 25 fps :( > >

Re: DRM map design

2005-07-13 Thread Egbert Eich
Dave Airlie writes: > > > > I've made a patch against the DRM code in CVS adding a few pieces that > > were missing. > > The code works for me on both radeon and r128. I've also tried to test > > mga however the mga code in CVS doesn't seem to work at all right now. > > My guess would be id