On 08/22/2012 07:26 PM, Ian Romanick wrote:
> From: Ian Romanick
>
> This consolidates the tests and makes the emitted error message
> consistent.
>
> Signed-off-by: Ian Romanick
> ---
> src/mesa/main/api_validate.c | 46
> +-
> 1 files changed, 23 in
As with the previous commit.
This fixes the last crash in the piglit copyteximage test but there's
still some failures.
---
src/mesa/main/texcompress.c |8 ++--
src/mesa/main/texcompress_s3tc.c | 60 -
src/mesa/main/texcompress_s3tc.h | 32
Fix-up the texel fetch functions so that they handle 3D coords (as used for
array textures) and remove the "f_2d" part from their names.
Helps fix swrast crashes in piglit's copyteximage test. More to come.
---
src/mesa/main/texcompress.c | 16 +++---
src/mesa/main/texcompress_rgtc.c | 1
https://bugs.freedesktop.org/show_bug.cgi?id=52064
--- Comment #7 from Vadim Girlin 2012-08-23 02:50:54 UTC ---
Just to clarify how mesa build with and without these patches works for me:
With current mesa 'make install' (as root) creates that file, and then I have
to remove it manually before r
From: Ian Romanick
Signed-off-by: Ian Romanick
---
src/mesa/main/APIspec.xml |8
src/mesa/main/varray.c| 13 ++---
2 files changed, 6 insertions(+), 15 deletions(-)
diff --git a/src/mesa/main/APIspec.xml b/src/mesa/main/APIspec.xml
index 4657b3c..d19a2b0 100644
--- a
From: Ian Romanick
Signed-off-by: Ian Romanick
---
src/mesa/main/APIspec.xml |6 --
1 files changed, 0 insertions(+), 6 deletions(-)
diff --git a/src/mesa/main/APIspec.xml b/src/mesa/main/APIspec.xml
index 0316d4c..4657b3c 100644
--- a/src/mesa/main/APIspec.xml
+++ b/src/mesa/main/APIs
From: Ian Romanick
Signed-off-by: Ian Romanick
---
src/mesa/main/APIspec.xml |6 --
src/mesa/main/varray.c|3 ++-
2 files changed, 2 insertions(+), 7 deletions(-)
diff --git a/src/mesa/main/APIspec.xml b/src/mesa/main/APIspec.xml
index c08a82b..0316d4c 100644
--- a/src/mesa/mai
From: Ian Romanick
Signed-off-by: Ian Romanick
---
src/mesa/main/APIspec.xml |4
src/mesa/main/varray.c|3 ++-
2 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/src/mesa/main/APIspec.xml b/src/mesa/main/APIspec.xml
index 5201647..3d5f521 100644
--- a/src/mesa/main/
From: Ian Romanick
Signed-off-by: Ian Romanick
---
src/mesa/main/APIspec.xml |8
src/mesa/main/varray.c| 14 ++
2 files changed, 6 insertions(+), 16 deletions(-)
diff --git a/src/mesa/main/APIspec.xml b/src/mesa/main/APIspec.xml
index 4812758..c08a82b 100644
---
From: Ian Romanick
Signed-off-by: Ian Romanick
---
src/mesa/main/APIspec.xml |8
src/mesa/main/varray.c| 11 ++-
2 files changed, 6 insertions(+), 13 deletions(-)
diff --git a/src/mesa/main/APIspec.xml b/src/mesa/main/APIspec.xml
index 3d5f521..4812758 100644
--- a/s
From: Ian Romanick
Signed-off-by: Ian Romanick
---
src/mesa/main/APIspec.xml |7 ---
src/mesa/main/varray.c| 15 ---
2 files changed, 8 insertions(+), 14 deletions(-)
diff --git a/src/mesa/main/APIspec.xml b/src/mesa/main/APIspec.xml
index 6d4ae0d..5201647 100644
---
From: Ian Romanick
Signed-off-by: Ian Romanick
---
src/mesa/main/APIspec.xml | 22 --
1 files changed, 0 insertions(+), 22 deletions(-)
diff --git a/src/mesa/main/APIspec.xml b/src/mesa/main/APIspec.xml
index 1f6f35d..6d4ae0d 100644
--- a/src/mesa/main/APIspec.xml
+++ b/s
From: Ian Romanick
Signed-off-by: Ian Romanick
---
src/mesa/main/APIspec.xml |7 ---
1 files changed, 0 insertions(+), 7 deletions(-)
diff --git a/src/mesa/main/APIspec.xml b/src/mesa/main/APIspec.xml
index 904a6d8..1f6f35d 100644
--- a/src/mesa/main/APIspec.xml
+++ b/src/mesa/main/API
From: Ian Romanick
Signed-off-by: Ian Romanick
---
src/mesa/main/varray.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/src/mesa/main/varray.c b/src/mesa/main/varray.c
index 36d0eb8..a867c89 100644
--- a/src/mesa/main/varray.c
+++ b/src/mesa/main/varray.c
@@ -142,
From: Ian Romanick
Signed-off-by: Ian Romanick
---
src/mesa/main/varray.c | 28 +++-
1 files changed, 19 insertions(+), 9 deletions(-)
diff --git a/src/mesa/main/varray.c b/src/mesa/main/varray.c
index 327fabb..36d0eb8 100644
--- a/src/mesa/main/varray.c
+++ b/src/mes
From: Ian Romanick
This consolidates the tests and makes the emitted error message
consistent.
Signed-off-by: Ian Romanick
---
src/mesa/main/api_validate.c | 46 +-
1 files changed, 23 insertions(+), 23 deletions(-)
diff --git a/src/mesa/main/api_vali
https://bugs.freedesktop.org/show_bug.cgi?id=52064
--- Comment #6 from Brian Paterni 2012-08-23 02:09:23 UTC
---
(In reply to comment #3)
> Created attachment 65987 [details] [review]
> [PATCH] build: remove git_sha1.h.tmp after install
>
> Yeah, this file is really annoying...
>
> I'm not an
From: Ian Romanick
This is a bit of a hack. _mesa_meta_GenerateMipmap shouldn't even be
used in contexts where GL_GENERATE_MIPMAP doesn't exist (i.e., core
profile and ES2) because it uses fixed-function, and fixed-function
doesn't exist there either!
A GLSL-based _mesa_meta_GenerateMipmap shou
https://bugs.freedesktop.org/show_bug.cgi?id=52064
--- Comment #5 from Vadim Girlin 2012-08-23 01:56:01 UTC ---
(In reply to comment #4)
> Created attachment 65990 [details] [review]
> patch
>
> Is this attached patch sufficient?
AFAICS it requires 'make clean' between 'make install' and 'make'
---
src/gallium/drivers/r600/r600_hw_context.c | 16 ++
src/gallium/drivers/r600/r600_pipe.c |2 +
src/gallium/drivers/r600/r600_pipe.h |2 +
src/gallium/drivers/r600/r600_resource.h |1 +
src/gallium/drivers/r600/r600_state.c | 255 +++-
s
This one actually makes more sense and gives the expected value
for MSAA resolve.
---
src/gallium/drivers/r600/r600_state.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/gallium/drivers/r600/r600_state.c
b/src/gallium/drivers/r600/r600_state.c
index 8f6b0cd..cf7fa01
This adds the FMASK and CMASK buffers. They share the same resource
with color data.
COMPRESSION and FAST_CLEAR are always enabled if both FMASK and CMASK are
allocated. We initialize the CMASK to a "compressed" state (not "fast cleared"),
so that we can keep FAST_CLEAR enabled all the time.
Both
for consistency with the upcoming color decompression naming
---
src/gallium/drivers/r600/r600_blit.c | 18 +-
src/gallium/drivers/r600/r600_pipe.h |8
src/gallium/drivers/r600/r600_resource.h |2 +-
src/gallium/drivers/r600/r600_state_common.
The original samples positions took samples outside of the pixel boundary,
leading to dark pixels on the edge of the colorbuffer, among other things.
---
src/gallium/drivers/r600/evergreen_state.c | 32 ++--
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/
independent_blend_enable must be true, so that the colormask isn't replicated
in all colorbuffers.
---
src/gallium/drivers/r600/evergreen_state.c |1 +
1 file changed, 1 insertion(+)
diff --git a/src/gallium/drivers/r600/evergreen_state.c
b/src/gallium/drivers/r600/evergreen_state.c
index 39
---
src/gallium/auxiliary/util/u_blitter.c |1 +
1 file changed, 1 insertion(+)
diff --git a/src/gallium/auxiliary/util/u_blitter.c
b/src/gallium/auxiliary/util/u_blitter.c
index a95e1b5..25c7119 100644
--- a/src/gallium/auxiliary/util/u_blitter.c
+++ b/src/gallium/auxiliary/util/u_blitter.c
This series adds R700 MSAA support along with compression of MSAA colorbuffers
for R700 and Evergreen, which should save a lot of bandwidth with MSAA. There
are also some minor fixes.
Please review.
Marek Olšák (7):
gallium/u_blitter: initialize sample mask in resolve
r600g: set CB_
On 08/22/2012 05:01 PM, Matt Turner wrote:
.y/.c was a typo.
Lol. This patch is
Reviewed-by: Ian Romanick
I can't really comment on the other one. I don't know anything about
the OpenVG code.
---
configure.ac |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/
https://bugs.freedesktop.org/show_bug.cgi?id=52064
--- Comment #4 from Matt Turner 2012-08-23 01:25:12 UTC ---
Created attachment 65990
--> https://bugs.freedesktop.org/attachment.cgi?id=65990
patch
Is this attached patch sufficient?
--
Configure bugmail: https://bugs.freedesktop.org/userpre
https://bugs.freedesktop.org/show_bug.cgi?id=52064
--- Comment #3 from Vadim Girlin 2012-08-23 01:10:19 UTC ---
Created attachment 65987
--> https://bugs.freedesktop.org/attachment.cgi?id=65987
[PATCH] build: remove git_sha1.h.tmp after install
Yeah, this file is really annoying...
I'm not an
On Wed, Aug 22, 2012 at 5:32 PM, Ian Romanick wrote:
> On 08/21/2012 10:49 PM, Eric Anholt wrote:
>> I don't like the idea of losing 16-wide on apps where it might have
>> succeeded if we just tried. Note that a chunk of register space gets
>> eaten by things that don't scale with number of pixel
On 08/21/2012 10:49 PM, Eric Anholt wrote:
Kenneth Graunke writes:
16-wide programs use roughly twice as many registers as 8-wide, and we
don't support spilling in 16-wide. So if an 8-wide program uses more
than half the available GRFs, the 16-wide one almost certainly will fail
to compile du
On Tue, Aug 21, 2012 at 7:28 PM, Brian Paul wrote:
> If a proxy texture call generates a regular GL error, we should not
> clear the proxy image's width/height/depth/format fields. Use a new
> PROXY_ERROR token to distinguish proxy errors from regular GL errors.
>
> Some additional clean-ups coul
.y/.c was a typo.
---
configure.ac |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/configure.ac b/configure.ac
index 9bf4e1e..5a83241 100644
--- a/configure.ac
+++ b/configure.ac
@@ -55,7 +55,7 @@ fi
AC_PROG_YACC
AC_PATH_PROG([YACC_INST], $YACC)
-if test ! -f "$srcdir
---
configure.ac |4 ++
src/mapi/vgapi/Makefile| 94
src/mapi/vgapi/Makefile.am | 62 +
src/mapi/vgapi/vg.pc.in| 12 +++---
4 files changed, 72 insertions(+), 100 deletions(-)
delete mode 1006
On Tue, Aug 21, 2012 at 7:28 PM, Brian Paul wrote:
> When calling glTexImage() with a proxy target most error conditions should
> generate a GL error. We were erroneously doing the proxy-error behaviour
> (where we zeroed-out the image's width/height/depth/format fields) in too
> many places.
>
>
From: Paulo Alcantara
Date: Fri, 17 Aug 2012 14:08:10 -0300
> The segmentation fault occurs when DRI2 is not loaded up and
> dri2_setup_screen() function deferences dri2_dpy->dri2 (since it's NULL
> at this point).
>
> This patch fixes the segmentation fault by checking if dri2 pointer is
> not
Paul Berry writes:
> On 22 August 2012 12:35, Eric Anholt wrote:
>
>> Paul Berry writes:
>>
>> > Previously, when performing a fast depth clear, we would also clear
>> > the miptree's resolve map. This destroyed important information,
>> > since the resolve map contains information about neede
On 20 August 2012 16:59, Anuj Phogat wrote:
> Render Target Write message should include source zero alpha value when
> sample-alpha-to-coverage is enabled for an FBO with multiple render
> targets.
> Source zero alpha value is used as fragment coverage for all the render
> targets.
>
> This pat
On 20 August 2012 16:13, Chad Versace wrote:
> Do all pre-draw hiz resolves *after* the renderbuffers are resized by
> intel_prepare_render. Otherwise, we may resolve buffers that are
> immediately discarded afterwards.
>
> Fixes the assertion failure below when resizing windows in KDE and under
On 08/22/2012 01:48 PM, Matt Turner wrote:
From: Tapani Pälli
Patches changes mesa to use 'HAVE_DLOPEN' defined by configure and Android.mk
instead of _GNU_SOURCE for detecting dlopen capability. This makes dlopen to
work also on Android where _GNU_SOURCE is not defined.
[mattst88] v2: HAVE_DLO
On 22 August 2012 12:35, Eric Anholt wrote:
> Paul Berry writes:
>
> > Previously, when performing a fast depth clear, we would also clear
> > the miptree's resolve map. This destroyed important information,
> > since the resolve map contains information about needed resolves for
> > all levels
No point in having an extra function call for inlinable functions.
Cc: Tapani Pälli
---
src/mesa/SConscript|1 -
src/mesa/main/dlopen.c | 112
src/mesa/main/dlopen.h | 83 ---
src/mesa/sources.mak |
From: Tapani Pälli
Patches changes mesa to use 'HAVE_DLOPEN' defined by configure and Android.mk
instead of _GNU_SOURCE for detecting dlopen capability. This makes dlopen to
work also on Android where _GNU_SOURCE is not defined.
[mattst88] v2: HAVE_DLOPEN is sufficient for including dlfcn.h, rem
https://bugs.freedesktop.org/show_bug.cgi?id=29613
--- Comment #3 from Kevin Hobbs 2012-08-22 19:43:59 UTC ---
(In reply to comment #2)
> Actually, I've just pushed it to master, so try that.
I'm experimenting under the assumption that your patch will allow me to build
libGL (dri) and libOSMesa
Paul Berry writes:
> Previously, when performing a fast depth clear, we would also clear
> the miptree's resolve map. This destroyed important information,
> since the resolve map contains information about needed resolves for
> all levels and layers of the miptree, whereas a depth clear only
>
https://bugs.freedesktop.org/show_bug.cgi?id=53835
--- Comment #9 from Kevin Hobbs 2012-08-22 19:10:10 UTC ---
(In reply to comment #8)
> Just pushed my branch. Should be fixed.
Yup, this seems to work.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are
Makefiles before .pc files before directories. Alphabetize files of the
same type.
---
configure.ac | 42 +-
1 files changed, 21 insertions(+), 21 deletions(-)
diff --git a/configure.ac b/configure.ac
index 59e8874..c1a8932 100644
--- a/configure.ac
+++ b
Xlib-GLX and OSMesa support static building.
---
configure.ac|2 ++
src/mesa/drivers/osmesa/Makefile.am |2 ++
src/mesa/drivers/x11/Makefile.am|2 ++
3 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/configure.ac b/configure.ac
index 46e9527..ad
---
src/mesa/drivers/osmesa/Makefile.am |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/src/mesa/drivers/osmesa/Makefile.am
b/src/mesa/drivers/osmesa/Makefile.am
index 3e2f2dc..1ceff88 100644
--- a/src/mesa/drivers/osmesa/Makefile.am
+++ b/src/mesa/drivers/osmesa/Makefile
Can be used by other modules.
---
configure.ac|7 ---
src/mesa/drivers/osmesa/Makefile.am |2 +-
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/configure.ac b/configure.ac
index c1a8932..46e9527 100644
--- a/configure.ac
+++ b/configure.ac
@@ -11
https://bugs.freedesktop.org/show_bug.cgi?id=53946
nkalk...@web.de changed:
What|Removed |Added
AssignedTo|mesa-dev@lists.freedesktop. |i...@freedesktop.org
From: Rob Bradford
Following on from 61e95b8a5f8524c7ff726f92ef6edc6b6bb35196 that always adds
__DRI_IMAGE_USE_SHARE to every bo created. We need to adjust the test that
checks that __DRI_IMAGE_USE_WRITE is only set on cursors - since that is the
only place it is supported.
This fixes gbm_bo_cre
https://bugs.freedesktop.org/show_bug.cgi?id=52513
Matt Turner changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugs.freedesktop.org/show_bug.cgi?id=53835
Matt Turner changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugs.freedesktop.org/show_bug.cgi?id=29613
--- Comment #2 from Matt Turner 2012-08-22 18:08:36 UTC ---
Actually, I've just pushed it to master, so try that.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
Yo
On 08/22/2012 09:52 AM, Matt Turner wrote:
On Thu, Aug 9, 2012 at 8:09 AM, Brian Paul wrote:
As of commit 9f7b3d171306ed2ae588e1a4145c5a364cf986ff, when I try to
configure and build with:
Do you want to try the first 6 (of 10) patches I sent to the list the
other day? They should fix this.
https://bugs.freedesktop.org/show_bug.cgi?id=29613
Matt Turner changed:
What|Removed |Added
CC||matts...@gmail.com
--- Comment #1 from Mat
https://bugs.freedesktop.org/show_bug.cgi?id=53946
Bug #: 53946
Summary: [i965] guardband clipping issue on Sandybridge
Classification: Unclassified
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
On Wed, 2012-08-22 at 19:54 +0400, Vadim Girlin wrote:
> On Wed, 2012-08-22 at 11:31 -0400, Alex Deucher wrote:
> > On Wed, Aug 22, 2012 at 11:24 AM, Vadim Girlin
> > wrote:
> > > On Wed, 2012-08-22 at 11:23 +0300, Maxim Levitsky wrote:
> > >> Currently Gallium has no way to activate the
> > >>
On Wed, Aug 22, 2012 at 11:54 AM, Vadim Girlin wrote:
> On Wed, 2012-08-22 at 11:31 -0400, Alex Deucher wrote:
>> On Wed, Aug 22, 2012 at 11:24 AM, Vadim Girlin wrote:
>> > On Wed, 2012-08-22 at 11:23 +0300, Maxim Levitsky wrote:
>> >> Currently Gallium has no way to activate the
>> >> 'force_gls
On Wed, 2012-08-22 at 11:31 -0400, Alex Deucher wrote:
> On Wed, Aug 22, 2012 at 11:24 AM, Vadim Girlin wrote:
> > On Wed, 2012-08-22 at 11:23 +0300, Maxim Levitsky wrote:
> >> Currently Gallium has no way to activate the
> >> 'force_glsl_extensions_warn' workaround that allows
> >> buggy apps tha
On Wed, 2012-08-22 at 18:53 +0300, Maxim Levitsky wrote:
> On Wed, 2012-08-22 at 08:48 -0600, Brian Paul wrote:
> > On 08/22/2012 02:23 AM, Maxim Levitsky wrote:
> > > Unfortunelly some buggy programs use extensions without asking ether for
> > > proper GLSL version nor ask for particular extensi
On Wed, 2012-08-22 at 08:48 -0600, Brian Paul wrote:
> On 08/22/2012 02:23 AM, Maxim Levitsky wrote:
> > Unfortunelly some buggy programs use extensions without asking ether for
> > proper GLSL version nor ask for particular extension.
> >
> > Moreover the force_glsl_extensions_warn hack is only e
On Thu, Aug 9, 2012 at 8:09 AM, Brian Paul wrote:
> As of commit 9f7b3d171306ed2ae588e1a4145c5a364cf986ff, when I try to
> configure and build with:
Do you want to try the first 6 (of 10) patches I sent to the list the
other day? They should fix this.
On Wed, Aug 22, 2012 at 3:21 AM, Maarten Lankhorst
wrote:
> And build gallium shared :)
Seems reasonable to me, given that we do this for dricore.
I've got a bunch of build patches waiting for review, so I'd
appreciate holding this until those patches go in.
I'm going to try to automake Gallium
Previously, when performing a fast depth clear, we would also clear
the miptree's resolve map. This destroyed important information,
since the resolve map contains information about needed resolves for
all levels and layers of the miptree, whereas a depth clear only
applies to a single level/layer
There are three possible resolve map states for each (level, layer) of
a depth miptree: "needs HiZ resolve", "needs depth resolve", and
"needs neither". When HiZ was first implemented on i965, any attempt
to directly transition between "needs HiZ resolve" and "needs depth
resolve" without passing
On Wed, Aug 22, 2012 at 11:24 AM, Vadim Girlin wrote:
> On Wed, 2012-08-22 at 11:23 +0300, Maxim Levitsky wrote:
>> Currently Gallium has no way to activate the
>> 'force_glsl_extensions_warn' workaround that allows
>> buggy apps that use GLSL extensions without asking for them to work.
>>
>> Sinc
On Wed, 2012-08-22 at 11:23 +0300, Maxim Levitsky wrote:
> Currently Gallium has no way to activate the
> 'force_glsl_extensions_warn' workaround that allows
> buggy apps that use GLSL extensions without asking for them to work.
>
> Since gallium mesa state tracker is essentially split into two,
>
On Mit, 2012-08-22 at 08:32 -0600, Brian Paul wrote:
> On 08/22/2012 04:21 AM, Maarten Lankhorst wrote:
> > And build gallium shared :)
> >
> > TODO: it seems ugly that all xvmc/vdpau/va drivers specify libgallium.a/so
> > directly, maybe it is better to move it out from there?
>
> The problem wi
On 08/22/2012 02:23 AM, Maxim Levitsky wrote:
Unfortunelly some buggy programs use extensions without asking ether for
proper GLSL version nor ask for particular extension.
Moreover the force_glsl_extensions_warn hack is only effective for some
extensions (GL_EXT_texture_array) but unfortunelly
On 08/22/2012 02:23 AM, Maxim Levitsky wrote:
Currently Gallium has no way to activate the
'force_glsl_extensions_warn' workaround that allows
buggy apps that use GLSL extensions without asking for them to work.
Since gallium mesa state tracker is essentially split into two,
(dri (src/gallium/st
On 08/22/2012 02:23 AM, Maxim Levitsky wrote:
From: Carl-Philip Haensch
This fixes fetching driconf options from the gallium drivers.
Patch written by, Carl-Philip Haensch
(http://lists.freedesktop.org/archives/mesa-dev/2011-May/007743.html)
Signed-off-by: Maxim Levitsky
---
.../state_tracke
On 08/22/2012 04:21 AM, Maarten Lankhorst wrote:
And build gallium shared :)
TODO: it seems ugly that all xvmc/vdpau/va drivers specify libgallium.a/so
directly, maybe it is better to move it out from there?
The problem with a separate libgallium.so is it's yet another
component that has to b
On 08/22/2012 04:02 AM, Maarten Lankhorst wrote:
Not my patch, but fixes a build error I encountered on quantal.
From 7e2e29c67f8fc8ec72c2dc8544428fdd86b21353 Mon Sep 17 00:00:00 2001
From: Olivier Blin
Date: Sat, 4 Aug 2012 00:29:45 +0200
Subject: [PATCH] gallium: only link static archives bet
For the series:
Reviewed-by: Michel Dänzer
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Debian, X and DRI developer
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
Preventing piglit's draw-vertices test from hanging the GPU.
Signed-off-by: Christian König
---
src/gallium/drivers/radeonsi/si_state.c | 68 ++-
1 file changed, 58 insertions(+), 10 deletions(-)
diff --git a/src/gallium/drivers/radeonsi/si_state.c
b/src/gallium/d
We need to enable at least one interpolation mode,
otherwise the GPU will hang.
Signed-off-by: Christian König
---
src/gallium/drivers/radeonsi/si_state_draw.c | 17 ++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/src/gallium/drivers/radeonsi/si_state_draw.c
b
And build gallium shared :)
TODO: it seems ugly that all xvmc/vdpau/va drivers specify libgallium.a/so
directly, maybe it is better to move it out from there?
diff --git a/configs/current.in b/configs/current.in
index c490842..73d08be 100644
--- a/configs/current.in
+++ b/configs/current.in
@@ -1
https://bugs.freedesktop.org/show_bug.cgi?id=53884
--- Comment #7 from Lauri Kasanen 2012-08-22 10:16:15
UTC ---
Okay, the corruption is due to the occlusion queries. I found that disabling
those removed the corruption in all cases.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.
Not my patch, but fixes a build error I encountered on quantal.
>From 7e2e29c67f8fc8ec72c2dc8544428fdd86b21353 Mon Sep 17 00:00:00 2001
From: Olivier Blin
Date: Sat, 4 Aug 2012 00:29:45 +0200
Subject: [PATCH] gallium: only link static archives between ld start/end group
options
llvmpipe test pr
Hey,
2 patches in the series, first is to fix/workaround a build error with
grouping and dynamic libraries, I found it on bugzilla.
The second one builds libgallium.so as a shared library to save some space.
I don't know what the full impact is and if there are some globals that
might get confuse
Unfortunelly some buggy programs use extensions without asking ether for
proper GLSL version nor ask for particular extension.
Moreover the force_glsl_extensions_warn hack is only effective for some
extensions (GL_EXT_texture_array) but unfortunelly isnt effective for other
extensions (I suspect t
Currently Gallium has no way to activate the
'force_glsl_extensions_warn' workaround that allows
buggy apps that use GLSL extensions without asking for them to work.
Since gallium mesa state tracker is essentially split into two,
(dri (src/gallium/state_trackers/dri) and mesa (src/mesa/state_track
From: Carl-Philip Haensch
This fixes fetching driconf options from the gallium drivers.
Patch written by, Carl-Philip Haensch
(http://lists.freedesktop.org/archives/mesa-dev/2011-May/007743.html)
Signed-off-by: Maxim Levitsky
---
.../state_trackers/dri/common/dri_context.c|5 +++--
Hi, just sending few hacky patches I made while wrestling
with Unigine demos.
First patch, fixes long standing issue of using driconf GUI with
Gallium drivers. I stumbled upon it long ago.
Now I fixed swrast to work with it too.
Second patch allows to use GLSL warning mode for shaders that dont
87 matches
Mail list logo