> From: nhaeh...@gmail.com
> To: mesa3d-dev@lists.sourceforge.net
> Subject: Re: [Mesa3d-dev] [PATCH] added provoking-vertex test.
> Date: Fri, 31 Jul 2009 21:50:09 +0200
> CC: shran...@hotmail.com
>
> Hi!
>
> I apologize for the slow reply. This looks fine, except for one thing:
>
> Am Wedne
On 31.07.2009 17:36, Terry Barnaby wrote:
> I have just compiled/installed the latest drm/mesa/xf86-video-ati code from
> git
> under Fedora 11 on a system with an ATI Technologies Inc RV280 [Radeon 9200
> PRO]
> graphics board.
>
> 2D appears fine. 3D is quite broken.
>
> gxlgears runs showin
>>Have you tried a clean rebuild? I think there may be a broken
dependency in src/glx/x11/
OK, "make clean" fixed it. Thanks !
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Sim
Bridgman, John wrote:
>>> While testing the r600 mesa driver I noticed that glxgears had
>>> recently started segfaulting on exit. Looks like commit
> e87320b5e033...
>>> (July 30 14:22:57 GMT) seems to be where the problem starts.
>>> Is anyone else seeing this behaviour ?
>
> Program receive
>>While testing the r600 mesa driver I noticed that glxgears had
>>recently started segfaulting on exit. Looks like commit
e87320b5e033...
>>(July 30 14:22:57 GMT) seems to be where the problem starts.
>>Is anyone else seeing this behaviour ?
Program received signal SIGSEGV, Segmentation fault
While testing the r600 mesa driver I noticed that glxgears had recently
started segfaulting on exit. Looks like commit e87320b5e033... (July 30
14:22:57 GMT) seems to be where the problem starts.
Is anyone else seeing this behaviour ?
---
Hi!
I apologize for the slow reply. This looks fine, except for one thing:
Am Wednesday 22 July 2009 00:20:25 schrieb Ben Holmes:
> +static void
> +Init()
> +{
> +
> + glewInit();
> + //piglit_require_extension("GL_EXT_provoking_vertex");
> + pglProvokingVertexEXT = (PFNGLPROVOKINGVER
Pushed, thanks.
Am Wednesday 29 July 2009 00:28:33 schrieb Pauli Nieminen:
> Signed-off-by: Pauli Nieminen
> ---
> src/mesa/drivers/dri/radeon/radeon_common.c |3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/src/mesa/drivers/dri/radeon/radeon_common.c
> b/src/mesa/
May I ask which version you're working against? The comment you modified in
your patch doesn't even exist on master as far as I can see.
In any case, I pushed the removal of lost_context.
cu,
Nicolai
Am Friday 31 July 2009 13:03:36 schrieb Pauli Nieminen:
> ---
> .../drivers/dri/radeon/radeon_
Am Friday 31 July 2009 10:26:47 schrieb Terry Barnaby:
> Hi,I have a problem with the Mesa DRI Radeon 300 driver in that I cannot
> use the blender application as the menus are not displayed correctly. See
> bug: https://bugs.freedesktop.org/show_bug.cgi?id=21774
>
> I would like to get this fixed
Brian Paul pisze:
> Michał Król wrote:
>
>> Brian Paul pisze:
>>
>>> I think I'd prefer to rename the "simple" LOOP2/ENDLOOP2 instructions
>>> as LOOP/ENDLOOP and call the above functions LOOP_COUNT/ENDLOOP_COUNT.
>>>
>>>
>>>
>> I am all for renaming, but just to make them shorte
On Fri, Jul 31, 2009 at 7:18 AM, Pauli Nieminen wrote:
> Hi.
>
> Some clean up to code so it is better thread safety even tough it is not
> 100% without locking or atomic operations. (Now it works same way as intel
> does recursion prevention)
> Another adittion is to make debug output to check if
I have just compiled/installed the latest drm/mesa/xf86-video-ati code from git
under Fedora 11 on a system with an ATI Technologies Inc RV280 [Radeon 9200 PRO]
graphics board.
2D appears fine. 3D is quite broken.
gxlgears runs showing about 500 frames/sec. However it shows as moving gears
for 1
Patrice Mandin wrote:
> Le Mon, 27 Jul 2009 15:55:26 -0600
> Brian Paul a écrit:
>
>>> Yep, just checked that. There must be another cause why I do not have
>>> any text rendered in progs/samples/blendeq with nouveau backend.
>> Have you implemented the TGSI_OPCODE_KIL instruction? That's critic
On 07/31/2009 02:15 PM, Roland Scheidegger wrote:
> On 31.07.2009 10:26, Terry Barnaby wrote:
>> Hi,I have a problem with the Mesa DRI Radeon 300 driver in that I cannot use
>> the
>> blender application as the menus are not displayed correctly. See bug:
>> https://bugs.freedesktop.org/show_bug.cg
Le Mon, 27 Jul 2009 15:55:26 -0600
Brian Paul a écrit:
> > Yep, just checked that. There must be another cause why I do not have
> > any text rendered in progs/samples/blendeq with nouveau backend.
>
> Have you implemented the TGSI_OPCODE_KIL instruction? That's critical
> to the glBitmap shad
Chia-I Wu wrote:
> On Thu, Jul 30, 2009 at 10:37:15AM -0600, Brian Paul wrote:
>> Chia-I Wu wrote:
>>> On Wed, Jul 29, 2009 at 09:21:15AM -0600, tom fogal wrote:
> -#if defined(_MSC_VER)
> +#if defined(__STDC_VERSION__) && __STDC_VERSION__ >= 199901L
> +# include
> +#elif defined(
On 07/31/2009 03:09 PM, Roland Scheidegger wrote:
> On 31.07.2009 15:35, Terry Barnaby wrote:
>> On 07/31/2009 02:15 PM, Roland Scheidegger wrote:
>>> On 31.07.2009 10:26, Terry Barnaby wrote:
Hi,I have a problem with the Mesa DRI Radeon 300 driver in that I cannot
use the
blender a
On 31.07.2009 15:35, Terry Barnaby wrote:
> On 07/31/2009 02:15 PM, Roland Scheidegger wrote:
>> On 31.07.2009 10:26, Terry Barnaby wrote:
>>> Hi,I have a problem with the Mesa DRI Radeon 300 driver in that I cannot
>>> use the
>>> blender application as the menus are not displayed correctly. See
Michał Król wrote:
> Brian Paul pisze:
>> I think I'd prefer to rename the "simple" LOOP2/ENDLOOP2 instructions
>> as LOOP/ENDLOOP and call the above functions LOOP_COUNT/ENDLOOP_COUNT.
>>
>>
>
> I am all for renaming, but just to make them shorter, what about the
> following renaming?
>
> L
Pauli Nieminen wrote:
> ---
> .../drivers/dri/radeon/radeon_common_context.h |1 -
> src/mesa/drivers/dri/radeon/radeon_lock.c |4 +---
> 2 files changed, 1 insertions(+), 4 deletions(-)
>
> diff --git a/src/mesa/drivers/dri/radeon/radeon_common_context.h
> b/src/mesa/driver
On 31.07.2009 10:26, Terry Barnaby wrote:
> Hi,I have a problem with the Mesa DRI Radeon 300 driver in that I cannot use
> the
> blender application as the menus are not displayed correctly. See bug:
> https://bugs.freedesktop.org/show_bug.cgi?id=21774
>
> I would like to get this fixed as I nee
Brian Paul pisze:
> I think I'd prefer to rename the "simple" LOOP2/ENDLOOP2 instructions
> as LOOP/ENDLOOP and call the above functions LOOP_COUNT/ENDLOOP_COUNT.
>
>
I am all for renaming, but just to make them shorter, what about the
following renaming?
LOOP => FORLOOP
ENDLOOP => ENDFOR
B
Hi.
Some clean up to code so it is better thread safety even tough it is not
100% without locking or atomic operations. (Now it works same way as intel
does recursion prevention)
Another adittion is to make debug output to check if DEBUG_SANITY is set.
Whole lock debugging is compiled out if there
---
.../drivers/dri/radeon/radeon_common_context.h |1 -
src/mesa/drivers/dri/radeon/radeon_lock.c |4 +---
2 files changed, 1 insertions(+), 4 deletions(-)
diff --git a/src/mesa/drivers/dri/radeon/radeon_common_context.h
b/src/mesa/drivers/dri/radeon/radeon_common_context.h
Hi,I have a problem with the Mesa DRI Radeon 300 driver in that I cannot use
the
blender application as the menus are not displayed correctly. See bug:
https://bugs.freedesktop.org/show_bug.cgi?id=21774
I would like to get this fixed as I need to be able to run blender at a
reasonable speed on
26 matches
Mail list logo
