[Bug 10303] glFogCoordPointer broken in DRI Radeon R300 driver

2007-03-17 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=10303 --- Comment #6 from [EMAIL PROTECTED] 2007-03-17 05:32 PST --- Dave Airlie already committed this. Commit 6a9b0cd0b43ba01b24871ec1fa155e192ddeaa56. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- Y

Re: [Mesa3d-dev] Announcing Piglit, an automated testing framework

2007-03-17 Thread Brian Paul
Nicolai Haehnle wrote: > Hello, > > back when I was actively working on DRI drivers almost three years > ago, I always felt uneasy about the fact that I didn't have an > extensive array of tests that I could rely on to test for regressions. > > Now I've decided to do something about it. I've take

compiling new xf86-video-intel drive

2007-03-17 Thread Sergio Monteiro Basto
Hi , I need your help , I am trying compile intel video drive and give me this: checking for xf86Modes.h... no symlink mode code configure: error: Must have X server >= 1.3 source tree for mode setting code. Please specify --with-xserver-source + exit 1 what I need upgrade is just xorg-x11-ser

Re: compiling new xf86-video-intel drive

2007-03-17 Thread Jesse Barnes
On Saturday, March 17, 2007, Sergio Monteiro Basto wrote: > Hi , > I need your help , I am trying compile intel video drive and give me > this: > > checking for xf86Modes.h... no > symlink mode code > configure: error: Must have X server >= 1.3 source tree for mode setting > code. Please specify --

Re: [Mesa3d-dev] Announcing Piglit, an automated testing framework

2007-03-17 Thread Oliver McFadden
I notice some failures with the example tests (R300) that seem to just be slight precision errors; I think you should add a margin for error because usually the hardware will implement things in a faster, perhaps less precise way. This lower precision is still "good enough", though. On 3/17/07,

Re: compiling new xf86-video-intel drive

2007-03-17 Thread Keith Packard
On Sat, 2007-03-17 at 16:41 +, Sergio Monteiro Basto wrote: > Hi , > I need your help , I am trying compile intel video drive and give me > this: > > checking for xf86Modes.h... no > symlink mode code > configure: error: Must have X server >= 1.3 source tree for mode setting > code. Please

Re: compiling new xf86-video-intel drive

2007-03-17 Thread Sergio Monteiro Basto
On Sat, 2007-03-17 at 12:44 -0700, Keith Packard wrote: > On Sat, 2007-03-17 at 16:41 +, Sergio Monteiro Basto wrote: > > Hi , > > I need your help , I am trying compile intel video drive and give me > > this: > > > > checking for xf86Modes.h... no > > symlink mode code > > configure: error

[PATCH] [r300] Fix reordering of fragment program instructions and register allocation

2007-03-17 Thread Nicolai Haehnle
There were a number of bugs related to the pairing of vector and scalar operations where swizzles ended up using the wrong source register, or an instruction was moved forward and ended up overwriting an aliased register. The new algorithm for register allocation is slightly conservative and may

Re: [PATCH] [r300] Fix reordering of fragment program instructions and register allocation

2007-03-17 Thread Oliver McFadden
This patch seems to break one of my longer fragment programs. I believe this is because it's running out of registers, but I haven't looked into it in detail yet. I think this patch should be committed, but directly followed by a patch to reduce the number of registers used. On 3/18/07, Nicolai

Re: [PATCH] [r300] Fix reordering of fragment program instructions and register allocation

2007-03-17 Thread Oliver McFadden
Another thought; the same changed are probably needed for the vertprog code. I think there are also a lot of bugs there. On 3/18/07, Oliver McFadden <[EMAIL PROTECTED]> wrote: > This patch seems to break one of my longer fragment programs. I believe this > is > because it's running out of registe

r500 progress?

2007-03-17 Thread Brandon Sharitt
I remember reading something about Jerome Glisse leading up an effort too bring support to r500 based cards, though I don't recall if it was "officially" happening with in the DRI development process, or just a side effort for now to be folded in once working. Anyway, I would like find some way to