cso_cache_delete checks if pipe has bind_vertex_sampler_states and
set_vertex_sampler_views so do the same in tr_context.
This avoids a segfault when tracing nvfx driver on piglit
glx-destroycontext-2
---
src/gallium/drivers/trace/tr_context.c |6 ++
1 files changed, 6 insertions(+), 0 de
Pass pipe_context rather than pipe_screen to util_surfaces_get and
util_surfaces_do_get so that they can check whether the saved pipe_surface
have the current context, and init properly a new pipe_surface with the
current context.
pipe_context is also passed to pipe_surface_reset and pipe_surface_
- pipe_surface->context not initialized in nvfx_miptree_surface_new
Should util_surfaces_get handle this initialization and take a pipe_context
rather than a pipe_screen ?
- ns was not properly initialized in nvfx_miptree_surface_new
ns->offset == ~0 test was dead, the initialization of offset t
On Mon, Nov 1, 2010 at 2:34 PM, José Fonseca wrote:
> I've just pushed a long time requested improvement to scons build
> system.
>
> Now is simply a matter of naming what to build. For example:
>
> scons libgl-xlib
>
> scons libgl-gdi
>
> scons graw-progs
>
> scons llvmpipe
>
> and so on. And
able.py", line 83
print '/* This file is autogenerated by u_format_table.py from
u_format.csv. Do not edit directly. */'
^
SyntaxError: invalid syntax
File "util/u_half.py", line 59
print "const " + t + " " + n + "[" + str(l
On Sun, Sep 26, 2010 at 10:42 PM, Dan Nicholson wrote:
>
> Normally you do that because if the user has custom include paths, you
> want them to be at the beginning of the command line.
>
> It'd be nice if the llvm people could just use pkg-config instead of
> rolling their own config tool. I thou
On Fri, Sep 24, 2010 at 11:36 PM, Xavier Chantry
wrote:
> On Fri, Sep 24, 2010 at 3:15 PM, Luca Barbieri wrote:
>> Yes, that used to happen for me too.
>>
>> Just edit llvm-config to remove the offending text and ideally file a
>> bug on the LLVM bug tracker.
>&g
On Fri, Sep 24, 2010 at 3:15 PM, Luca Barbieri wrote:
> Yes, that used to happen for me too.
>
> Just edit llvm-config to remove the offending text and ideally file a
> bug on the LLVM bug tracker.
>
looks like nobled did this for me : http://llvm.org/bugs/show_bug.cgi?id=8220
thanks :)
It's sti
--cppflags ?
I found it weird that enabling or disabling gallium llvm resulted in
nv50 gallium built with different gcc flags.
From df82cdf0b9b6bd60ef47ddbf4b6d74d200382262 Mon Sep 17 00:00:00 2001
From: Xavier Chantry
Date: Fri, 24 Sep 2010 13:17:40 +0200
Subject: [PATCH] configure.ac : use llvm
On Thu, Jun 10, 2010 at 3:38 PM, Xavier Chantry
wrote:
>
> If anyone wants to rebase the whole nvfx-next-6b branch without
> temporaries on top of master, I will happily test that as well.
>
I just had a look and this rebase seems too complex for me to handle.
A better understandin
On Tue, Jun 8, 2010 at 8:49 PM, Xavier Chantry wrote:
> On Tue, Jun 8, 2010 at 8:36 PM, Corbin Simpson
> wrote:
>> Luca (and anybody else, especially nouveau people),
>>
>> Does anybody want to step up and look at the nvfx-next branches? In
>> IRC, we're look
On Tue, Jun 8, 2010 at 8:36 PM, Corbin Simpson
wrote:
> Luca (and anybody else, especially nouveau people),
>
> Does anybody want to step up and look at the nvfx-next branches? In
> IRC, we're looking over some of the parts that got merged to master
> (util/u_surfaces and util/u_dirty_surfaces) bu
Ok, after looking at how some other drivers were updated, I thought
nouveau needed bigger changes than that.
Jakob just pushed a simple build fix, and now nv50 builds and runs (almost ;)).
I just noticed 5 piglit regressions :
fbo/fbo-copypix
fbo/fbo-copyteximage
general/scissor-copypixels
texturi
On Tue, May 18, 2010 at 7:04 PM, Roland Scheidegger wrote:
> Hi,
>
> I plan to merge the gallium-msaa branch to master soon.
> It's actually a bit of a misnomer since the conceptually more important
> changes in there are about blits...
>
> Here's a short summary what this is about:
> blits now op
Patrice reported this a few days ago in nouveau channel and wiki,
using xorg 1.7 and probably nvfx driver.
I can reproduce with xorg 1.7 and nv50 with current git master.
Window resizing (for example with glxgears or any mesa demos/*) is
broken, as seen in the following picture :
http://omploader.
On Thu, May 6, 2010 at 6:23 PM, Brian Paul wrote:
>
> As I wrote in bug report https://bugs.freedesktop.org/show_bug.cgi?id=27989,
> there's something funny with that test. Even with NVIDIA's driver, it
> sometimes passes and sometimes fails from one run to another. I'm hoping to
> get to that t
> On Tue, 2010-05-04 at 07:41 -0700, Jose Fonseca wrote:
>> Module: Mesa
>> Branch: master
>> Commit: dad962bafe8ffd7fdb35c28cfb8bbd5a297c8083
>> URL:
>> http://cgit.freedesktop.org/mesa/mesa/commit/?id=dad962bafe8ffd7fdb35c28cfb8bbd5a297c8083
>>
>> Author: José Fonseca
>> Date: Tue May 4 1
On Thu, May 6, 2010 at 1:46 PM, José Fonseca wrote:
> On Thu, 2010-05-06 at 04:13 -0700, Xavier Chantry wrote:
>> On Mon, May 3, 2010 at 12:56 AM, Xavier Chantry
>> wrote:
>> > These files are built with make and removed with make clean, so it does not
>>
On Mon, May 3, 2010 at 12:56 AM, Xavier Chantry
wrote:
> These files are built with make and removed with make clean, so it does not
> seem necessary to track them.
>
> Looking at the Makefile, it seems that the two u_indices_* files are handled
> similarly to u_format_srgb.c u_for
On Mon, May 3, 2010 at 9:11 PM, Brian Paul wrote:
>>
>> This commit also causes piglit fbo-3d test to fail with both llvmpipe
>> and nv50 gallium.
>> http://img163.imageshack.us/img163/535/fbo3d.png
>
> Can you retest now?
>
Yup, fbo-3d is back on both nv50 and llvmpipe/swrastg. Thanks !
This fixes flightgear assertion in dxt stubs :
Mesa warning: external dxt library not available: texstore_rgba_dxt3
util/u_format_s3tc.c:66:util_format_dxt3_rgba_fetch_stub: Assertion `0'
failed.
Only advertise for BIND_SAMPLER_VIEW to avoid very weird paths, according to
José Fonseca.
---
src/ga
On Sun, May 2, 2010 at 3:16 PM, Marek Olšák wrote:
> On Sat, May 1, 2010 at 11:31 PM, Maxim Levitsky
> wrote:
>>
>> This commit breaks compiz completely here on nvidia G50 (Geforce 8400M)
>> Compiz shows dark screen.
>> (Using nouveau drivers)
>>
>> Without this commit compiz works almost perfect
On Mon, May 3, 2010 at 1:20 AM, Chris Ball wrote:
> http://tinderbox.x.org/builds/2010-05-02-0034/logs/libGL/#build
>
> In file included from ../common/drisw_util.c:30:
> ../common/drisw_util.h:39:20: error: mtypes.h: No such file or directory
>
> In file included from ../common/drisw_util.c:30:
>
From: Luca Barbieri
Re-add commit 2d65a7caf97684aa654088c76a74b632fbd685fa
Signed-off-by: Xavier Chantry
---
src/gallium/auxiliary/util/u_format_s3tc.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/gallium/auxiliary/util/u_format_s3tc.c
b/src/gallium
Signed-off-by: Xavier Chantry
---
src/gallium/drivers/llvmpipe/.gitignore |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/src/gallium/drivers/llvmpipe/.gitignore
b/src/gallium/drivers/llvmpipe/.gitignore
index 257b72d..a1b6f56 100644
--- a/src/gallium/drivers
On Sun, May 2, 2010 at 10:17 PM, Dave Airlie wrote:
> On Mon, May 3, 2010 at 3:43 AM, Aaron Plattner wrote:
>> On Sun, May 02, 2010 at 02:39:07AM -0700, Dave Airlie wrote:
>>> On Fri, Apr 23, 2010 at 2:30 AM, Aaron Plattner
>>> wrote:
>>> > __glXInitializeVisualConfigFromTags doesn't skip the p
scons couldn't build nv50 as it uses -Werror=pointer-arith by default.
Signed-off-by: Xavier Chantry
---
src/gallium/drivers/nv50/nv50_push.c | 10 +-
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/src/gallium/drivers/nv50/nv50_push.c
b/src/gallium/drivers
On Fri, Apr 30, 2010 at 6:42 PM, Corbin Simpson
wrote:
>
> I think the big problem is the disconnect between VMWare and the rest
> of the developers in terms of communication. We all are on IRC
> extensively but at least Brian, Keith, Jose, and Vinson are not.
> Coincidentally, these are the peopl
On Thu, Apr 22, 2010 at 12:57 PM, wrote:
> Hello. I have old nvidia hardware (NV17) and noticed that some extensions
> are missing.They will be added in near future ? Anyone from nouveau
> developers actually working on driver for such old hw ???
A few months ago :
15:27 < curro_> hmm, or we cou
On Wed, Apr 14, 2010 at 10:38 PM, Brian Paul wrote:
> Xavier Chantry wrote:
>>
>> glActiveTexture is available only if the GL version is 1.3 or greater.
>
> Committed. Thanks.
>
> We should really have a new mailing list for piglit...
>
That would only wo
glMultiTexCoord4fv is available only if the GL version is 1.3 or
greater.
Signed-off-by: Xavier Chantry
---
tests/general/texunits.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/tests/general/texunits.c b/tests/general/texunits.c
index 01a5e27..1a5f67e 100644
glActiveTexture is available only if the GL version is 1.3 or greater.
Signed-off-by: Xavier Chantry
---
tests/bugs/fdo25614-genmipmap.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/tests/bugs/fdo25614-genmipmap.c b/tests/bugs/fdo25614-genmipmap.c
index 6f8c60e
A lot of apps segfaulted due to this missing initialization (including 64
piglit tests :).
Signed-off-by: Xavier Chantry
---
src/gallium/drivers/nvfx/nvfx_miptree.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/src/gallium/drivers/nvfx/nvfx_miptree.c
b/src/gallium
33 matches
Mail list logo