Signed-off-by: Ilia Mirkin
---
docs/GL3.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/GL3.txt b/docs/GL3.txt
index d9cc708..bf51e3a 100644
--- a/docs/GL3.txt
+++ b/docs/GL3.txt
@@ -107,7 +107,7 @@ GL 4.0:
GL_ARB_tessellation_shader not s
Signed-off-by: Ilia Mirkin
---
Tested on NVE6. Very strange that it seems to use 8 bits for offsets, vs 4
bits used by texelFetch. But this passes the piglit tests.
Will test on a NVCX before checking in, in case it's different
there. (Although that'd be surprising, given the similarities betwee
I guess I misunderstood that obj() call (my IDE is misbehaving on the
machine I was doing that work on which limited my ability to easily
find function definitions outside of the current file). C++ is pretty
unfamiliar to me and I guess that I figured that the obj() was some
alternative typecastin
From: Dave Airlie
This opcode provide support for GL_ARB_texture_query_lod,
Signed-off-by: Dave Airlie
[imirkin: rebase, docs update]
Signed-off-by: Ilia Mirkin
---
src/gallium/auxiliary/tgsi/tgsi_info.c | 1 +
src/gallium/docs/source/screen.rst | 2 ++
src/gallium/d
This is based on Dave's patches from his r600g-texture-gather branch. He also
has an r600 support patch, but I do not have access to that hardware. Tested
on NVA8 (GT218) and NVE6 (GK106) hardware.
Of note is that the instruction changed returned argument order starting with
nvc0. Perhaps it would
Signed-off-by: Ilia Mirkin
---
.../drivers/nouveau/codegen/nv50_ir_emit_gk110.cpp | 10 ++
.../drivers/nouveau/codegen/nv50_ir_emit_nvc0.cpp | 2 ++
.../nouveau/codegen/nv50_ir_lowering_nvc0.cpp | 41 ++
src/gallium/drivers/nouveau/nvc0/nvc0_screen.c | 3 +-
4
From: Dave Airlie
Add support for the LODQ texture instruction.
Signed-off-by: Dave Airlie
---
src/mesa/state_tracker/st_extensions.c | 3 ++-
src/mesa/state_tracker/st_glsl_to_tgsi.cpp | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/src/mesa/state_tracker/st_extens
Signed-off-by: Ilia Mirkin
---
src/gallium/drivers/nouveau/codegen/nv50_ir.h | 1 +
.../drivers/nouveau/codegen/nv50_ir_emit_nv50.cpp | 4
.../drivers/nouveau/codegen/nv50_ir_from_tgsi.cpp | 3 +++
.../nouveau/codegen/nv50_ir_lowering_nv50.cpp | 23 ++
.../
Signed-off-by: Ilia Mirkin
---
docs/GL3.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/GL3.txt b/docs/GL3.txt
index b7e4c87..d9cc708 100644
--- a/docs/GL3.txt
+++ b/docs/GL3.txt
@@ -97,7 +97,7 @@ GL 3.3 --- all DONE: i965, nv50, nvc0, r600, radeonsi
GL 4.0:
GLS
On Friday, 4 April 2014 11:31 AM, Dieter Nützel wrote:
>Mesa 10.2.0-devel (git-c6050ce)
>/opt/ogl-samples> ./build/release/gl-320-primitive-sprite
>Mesa warning: failed to remap glDebugMessageCallbackARB
>Mesa warning: failed to remap glDebugMessageControlARB
>Mesa warning: failed to remap gl
Fixes failures in Khronos OpenGL CTS test proxy_textures_invalid_samples
Cc:
Signed-off-by: Anuj Phogat
---
src/mesa/main/teximage.c | 16 +---
1 file changed, 13 insertions(+), 3 deletions(-)
diff --git a/src/mesa/main/teximage.c b/src/mesa/main/teximage.c
index 57a766f..aac3887 1
https://bugs.freedesktop.org/show_bug.cgi?id=77023
--- Comment #1 from Brian Paul ---
The problem is we're mapping the same texture (but different slices) multiple
times simultaneously. The state tracker doesn't support that.
This assertion fails if I put it in st_texture.c:
--- a/src/mesa/sta
Am 03.04.2014 22:53, schrieb Ian Romanick:
On 04/03/2014 07:35 AM, Dieter Nützel wrote:
Am 03.04.2014 04:16, schrieb Ian Romanick:
On 04/02/2014 06:13 PM, Dieter Nützel wrote:
Am 03.04.2014 01:19, schrieb Ian Romanick:
On 04/02/2014 03:43 PM, Dieter Nützel wrote:
Am 02.04.2014 08:12, schrieb
---
src/mesa/drivers/dri/i965/brw_fs_saturate_propagation.cpp | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/mesa/drivers/dri/i965/brw_fs_saturate_propagation.cpp
b/src/mesa/drivers/dri/i965/brw_fs_saturate_propagation.cpp
index eaecb45..4f3dcff 100644
--- a/src/mesa/dr
Which would lead to translating
mad vgrf9:F, vgrf3:F, u0:F, vgrf6:F
mov.sat vgrf7:F, -vgrf9:F
into
mad.sat vgrf9:F, vgrf3:F, u0:F, vgrf6:F
mov vgrf7:F, -vgrf9:F
Fixes some lighting effects in Dota2.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=76749
---
src/mes
ip needs to be initialized to start_ip - 1, since the first thing in the
main loop is ip++. Otherwise we would incorrectly propagate the saturate
from the mov to the mad:
mad a, b, c, d
mov.sat x, a
add y, z, a
---
src/mesa/drivers/dri/i965/brw_fs_saturate_propagation.cpp | 2 +-
Aaron Watry writes:
> This should fix a segfault in the case that you're not using ocl-icd.
>
> If you're using ocl-icd, make sure your version is new enough or you'll get
> the segfault before you even get to clover.
>
> The null de-ref seems to have been introduced in 10.1, but earlier versions
This should fix a segfault in the case that you're not using ocl-icd.
If you're using ocl-icd, make sure your version is new enough or you'll get
the segfault before you even get to clover.
The null de-ref seems to have been introduced in 10.1, but earlier versions
have have also been affected in
For TEX instructions, the set of samplers and sampler views should
be consistent. The XA state tracker sometimes passes an inconsistent
set of samplers and sampler views. Rather than assert and die, issue
a warning.
v2: add debugging code to detect inconsistent state.
---
src/gallium/drivers/sv
This patch changes the behavior of glGetAttribLocation(),
glGetFragDataLocation() and glGetFragDataIndex() functions.
Code changes handle the cases described in following example:
vertex shader:
layout(location = 1)in vec4[4] a;
void main()
{
}
fragment shader:
layout (location = 1) out vec4[4] c
Reviewed-by: Marek Olšák
Marek
On Thu, Apr 3, 2014 at 5:56 PM, Brian Paul wrote:
> As we do for sampler states in single_sampler_done() and many other
> CSO functions.
> ---
> src/gallium/auxiliary/cso_cache/cso_context.c | 11 ---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
On 04/03/2014 10:49 AM, Roland Scheidegger wrote:
Am 03.04.2014 16:56, schrieb Brian Paul:
For TEX instructions, the set of samplers and sampler views should
be consistent. The XA state tracker sometimes passes an inconsistent
set of samplers and sampler views. Rather than assert and die, issu
On 04/03/2014 02:42 PM, Ian Romanick wrote:
On 04/03/2014 12:57 AM, Chris Forbes wrote:
This was marked as somewhere we're deviating from the spec in order to
follow what nVIDIA does. Is there no longer a reason to?
Well... and is it still what NVIDIA does? :)
I have the NVIDIA 325.15 driver
From: Leo Liu
Signed-off-by: Leo Liu
---
src/gallium/drivers/radeon/radeon_vce.c| 22 +++---
src/gallium/drivers/radeon/radeon_vce.h| 3 +++
src/gallium/drivers/radeon/radeon_vce_40_2_2.c | 21 +++--
3 files changed, 37 insertions(+), 9 deletions
On 04/03/2014 07:35 AM, Dieter Nützel wrote:
> Am 03.04.2014 04:16, schrieb Ian Romanick:
>> On 04/02/2014 06:13 PM, Dieter Nützel wrote:
>>> Am 03.04.2014 01:19, schrieb Ian Romanick:
On 04/02/2014 03:43 PM, Dieter Nützel wrote:
> Am 02.04.2014 08:12, schrieb Timothy Arceri:
>> On Wed
Kristian: You had some thoughts on this. Could you share them with the
list? :)
On 03/27/2014 01:47 AM, Iago Toral Quiroga wrote:
> Commit 11baad35088dfd4bdabc1710df650dbfb413e7a3 produces a regression when
> switching a single context between multiple drawables.
>
> The problem is that we check
On 04/03/2014 12:57 AM, Chris Forbes wrote:
> This was marked as somewhere we're deviating from the spec in order to
> follow what nVIDIA does. Is there no longer a reason to?
Well... and is it still what NVIDIA does? :)
> On Thu, Apr 3, 2014 at 7:30 PM, Samuel Iglesias Gonsalvez
> wrote:
>> Acc
https://bugs.freedesktop.org/show_bug.cgi?id=76960
--- Comment #6 from Ian Romanick ---
(In reply to comment #5)
> I took the liberty of pushing Ian's fix.
Thanks, and sorry about the delay. I thought I pushed it yesterday after I got
Brian's Tested-by. :(
--
You are receiving this mail becau
Hello,
I'm looking at the EXT_swap_control extension; as far as I can tell, Mesa
does not support it (feel free to correct me if I'm wrong).
Given the fact, that both its precursors SGI_swap_control and MESA_swap_
control are implemented,
I wander - are there any deeper reasons for not suppor
Pretty neat!
- Original Message -
> Hi everyone,
>
> I've set up a readthedocs.org build to point at the gallium docs:
>
> https://urldefense.proofpoint.com/v1/url?u=http://gallium.readthedocs.org/en/latest/&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=NMr9uy2iTjWVixC0wOcYCWEIYhfo80qKwRgdodpoDz
https://bugs.freedesktop.org/show_bug.cgi?id=77023
Priority: medium
Bug ID: 77023
CC: bri...@vmware.com, jfons...@vmware.com,
srol...@vmware.com
Assignee: mesa-dev@lists.freedesktop.org
Summary: [llvmpipe] SIGSEGV
Wow this is great. Thanks for doing this
Starting to read through it all now
Mike
On 31 Mar 2014 17:43, "Ilia Mirkin" wrote:
> Hi everyone,
>
> I've set up a readthedocs.org build to point at the gallium docs:
>
> http://gallium.readthedocs.org/en/latest/
>
> I didn't find any publicly availabl
https://bugs.freedesktop.org/show_bug.cgi?id=76976
--- Comment #1 from Roland Scheidegger ---
I'm pretty sure that's because llvmpipe lacks the ability to clear just one rb
from the fb. The gallium interface lacked that too which made it impossible to
actually clear such mixed fbs in a useful way
On Wed, Apr 2, 2014 at 11:26 PM, Jonathan Gray wrote:
> On Wed, Apr 02, 2014 at 11:09:09PM -0700, Matt Turner wrote:
>> On Wed, Apr 2, 2014 at 10:22 PM, Jonathan Gray wrote:
>> > Don't hardcode /dev/dri/card0 but instead use the drm
>> > macros which allows the correct /dev/drm0 device to be
>> >
- Original Message -
> Am 03.04.2014 17:56, schrieb Brian Paul:
> > ---
> > src/gallium/drivers/llvmpipe/lp_state_sampler.c | 14 --
> > 1 file changed, 14 deletions(-)
> >
> > diff --git a/src/gallium/drivers/llvmpipe/lp_state_sampler.c
> > b/src/gallium/drivers/llvmpipe/
- Original Message -
> On 04/03/2014 08:57 AM, jfons...@vmware.com wrote:
> > From: José Fonseca
> >
> > This prevents buffer overflow w/ llvmpipe when running piglit
> >
> >bin/gl-3.2-layered-rendering-clear-color-all-types 1d_array single_level
> >-fbo -auto
> > ---
> > src/m
Am 03.04.2014 17:56, schrieb Brian Paul:
> ---
> src/gallium/drivers/llvmpipe/lp_state_sampler.c | 14 --
> 1 file changed, 14 deletions(-)
>
> diff --git a/src/gallium/drivers/llvmpipe/lp_state_sampler.c
> b/src/gallium/drivers/llvmpipe/lp_state_sampler.c
> index db8646c..09bc928
Am 03.04.2014 16:56, schrieb Brian Paul:
> For TEX instructions, the set of samplers and sampler views should
> be consistent. The XA state tracker sometimes passes an inconsistent
> set of samplers and sampler views. Rather than assert and die, issue
> a warning.
>
> Cc: "10.0" "10.1"
> ---
>
https://bugs.freedesktop.org/show_bug.cgi?id=76848
--- Comment #7 from Vinson Lee ---
attachment 96690 alone does not fix make check.
With all three patches applied, make check passes.
Tested-by: Vinson Lee
--
You are receiving this mail because:
You are the assignee for the bug.
___
Acked-by: Marek Olšák
Marek
On Tue, Mar 18, 2014 at 4:16 PM, Maarten Lankhorst
wrote:
> Use the recursive copy from emit_block_mov to allow constant declarations to
> work.
>
> This allows the following code to work without a weird crash:
>
> struct Foo {
> int value[1];
> };
>
> int actual_v
Am 03.04.2014 17:35, schrieb Roland Scheidegger:
> Am 03.04.2014 17:19, schrieb Brian Paul:
>> On 04/03/2014 08:57 AM, jfons...@vmware.com wrote:
>>> From: José Fonseca
>>>
>>> This prevents buffer overflow w/ llvmpipe when running piglit
>>>
>>>bin/gl-3.2-layered-rendering-clear-color-all-typ
We are checking for no-ops in the CSO module for both of these items
so there's no reason to do it in the driver.
---
src/gallium/drivers/svga/svga_pipe_sampler.c | 15 ---
1 file changed, 15 deletions(-)
diff --git a/src/gallium/drivers/svga/svga_pipe_sampler.c
b/src/gallium/drive
As we do for sampler states in single_sampler_done() and many other
CSO functions.
---
src/gallium/auxiliary/cso_cache/cso_context.c | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/src/gallium/auxiliary/cso_cache/cso_context.c
b/src/gallium/auxiliary/cso_cache/cs
---
src/gallium/drivers/llvmpipe/lp_state_sampler.c | 14 --
1 file changed, 14 deletions(-)
diff --git a/src/gallium/drivers/llvmpipe/lp_state_sampler.c
b/src/gallium/drivers/llvmpipe/lp_state_sampler.c
index db8646c..09bc928 100644
--- a/src/gallium/drivers/llvmpipe/lp_state_samp
---
src/gallium/drivers/softpipe/sp_state_sampler.c | 14 --
1 file changed, 14 deletions(-)
diff --git a/src/gallium/drivers/softpipe/sp_state_sampler.c
b/src/gallium/drivers/softpipe/sp_state_sampler.c
index 161e0e1..e512418 100644
--- a/src/gallium/drivers/softpipe/sp_state_samp
Am 03.04.2014 16:03, schrieb Leo Liu:
From: Leo Liu
Signed-off-by: Leo Liu
---
src/gallium/drivers/radeon/radeon_vce.c| 22 +++---
src/gallium/drivers/radeon/radeon_vce.h| 3 +++
src/gallium/drivers/radeon/radeon_vce_40_2_2.c | 6 --
3 files changed,
On Thu, Apr 3, 2014 at 11:00 AM, Thomas Hellstrom wrote:
> On 04/03/2014 04:49 PM, Rob Clark wrote:
>> On Thu, Apr 3, 2014 at 2:05 AM, Thomas Hellstrom
>> wrote:
>>> The xa version number had to be set in two places. In configure.ac and in
>>> xa_tracker.h. Furthermore, xa_tracker.h is an instal
Am 03.04.2014 17:19, schrieb Brian Paul:
> On 04/03/2014 08:57 AM, jfons...@vmware.com wrote:
>> From: José Fonseca
>>
>> This prevents buffer overflow w/ llvmpipe when running piglit
>>
>>bin/gl-3.2-layered-rendering-clear-color-all-types 1d_array
>> single_level -fbo -auto
>> ---
>> src/me
Am 03.04.2014 16:57, schrieb jfons...@vmware.com:
> From: José Fonseca
>
> This prevents buffer overflow w/ llvmpipe when running piglit
>
> bin/gl-3.2-layered-rendering-clear-color-all-types 1d_array single_level
> -fbo -auto
> ---
> src/mesa/state_tracker/st_atom_framebuffer.c | 19 +++
On 04/03/2014 08:57 AM, jfons...@vmware.com wrote:
From: José Fonseca
This prevents buffer overflow w/ llvmpipe when running piglit
bin/gl-3.2-layered-rendering-clear-color-all-types 1d_array single_level
-fbo -auto
---
src/mesa/state_tracker/st_atom_framebuffer.c | 19 +-
On 04/03/2014 08:41 AM, Brian Paul wrote:
On 04/03/2014 08:13 AM, Rob Clark wrote:
On Thu, Apr 3, 2014 at 10:07 AM, Brian Paul wrote:
On 04/02/2014 11:17 PM, Thomas Hellstrom wrote:
On 04/01/2014 05:04 PM, Rob Clark wrote:
From: Rob Clark
Add support to property handle solid-fill src and
On 04/03/2014 04:49 PM, Rob Clark wrote:
> On Thu, Apr 3, 2014 at 2:05 AM, Thomas Hellstrom
> wrote:
>> The xa version number had to be set in two places. In configure.ac and in
>> xa_tracker.h. Furthermore, xa_tracker.h is an installed header so we can't
>> use mesa internal defines. So therefor
What is the process for getting this committed?
I just upgraded from Oibaf PPA, to 0f641b...
8 hours mesa: remove redundant running of check_symbol_table()
It's super cool I can get recent snapshots, but I'm still building from
source.
On Wed, Apr 2, 2014 at 7:46 PM, Mike Mestnik wrote:
> Th
That seems to be the issue, I'll see about getting this patch applied.
On Wed, Apr 2, 2014 at 3:39 PM, Marek Olšák wrote:
> This is a known bug. See:
>
> https://bugs.freedesktop.org/show_bug.cgi?id=74868#c14
>
> Marek
>
> On Wed, Apr 2, 2014 at 12:30 AM, Mike Mestnik
> wrote:
> > http://bitly
From: José Fonseca
This prevents buffer overflow w/ llvmpipe when running piglit
bin/gl-3.2-layered-rendering-clear-color-all-types 1d_array single_level -fbo
-auto
---
src/mesa/state_tracker/st_atom_framebuffer.c | 19 +--
1 file changed, 17 insertions(+), 2 deletions(-)
di
For TEX instructions, the set of samplers and sampler views should
be consistent. The XA state tracker sometimes passes an inconsistent
set of samplers and sampler views. Rather than assert and die, issue
a warning.
Cc: "10.0" "10.1"
---
src/gallium/drivers/svga/svga_state_fs.c | 12
On Thu, Apr 3, 2014 at 10:41 AM, Brian Paul wrote:
> On 04/03/2014 08:13 AM, Rob Clark wrote:
>>
>> On Thu, Apr 3, 2014 at 10:07 AM, Brian Paul wrote:
>>>
>>> On 04/02/2014 11:17 PM, Thomas Hellstrom wrote:
On 04/01/2014 05:04 PM, Rob Clark wrote:
>
>
> From: Rob Clark
On Thu, Apr 3, 2014 at 2:05 AM, Thomas Hellstrom wrote:
> The xa version number had to be set in two places. In configure.ac and in
> xa_tracker.h. Furthermore, xa_tracker.h is an installed header so we can't
> use mesa internal defines. So therefore, at configure time, modify the
> xa_tracker.h h
On 04/03/2014 08:13 AM, Rob Clark wrote:
On Thu, Apr 3, 2014 at 10:07 AM, Brian Paul wrote:
On 04/02/2014 11:17 PM, Thomas Hellstrom wrote:
On 04/01/2014 05:04 PM, Rob Clark wrote:
From: Rob Clark
Add support to property handle solid-fill src and/or mask. Without this
we fallback to sw a
Am 03.04.2014 04:16, schrieb Ian Romanick:
On 04/02/2014 06:13 PM, Dieter Nützel wrote:
Am 03.04.2014 01:19, schrieb Ian Romanick:
On 04/02/2014 03:43 PM, Dieter Nützel wrote:
Am 02.04.2014 08:12, schrieb Timothy Arceri:
On Wed, 2014-04-02 at 00:56 +0200, Dieter Nützel wrote:
Hello Ian, hell
On Thu, Apr 3, 2014 at 10:07 AM, Brian Paul wrote:
> On 04/02/2014 11:17 PM, Thomas Hellstrom wrote:
>>
>> On 04/01/2014 05:04 PM, Rob Clark wrote:
>>>
>>> From: Rob Clark
>>>
>>> Add support to property handle solid-fill src and/or mask. Without this
>>> we fallback to sw a lot for common thing
On 04/02/2014 11:17 PM, Thomas Hellstrom wrote:
On 04/01/2014 05:04 PM, Rob Clark wrote:
From: Rob Clark
Add support to property handle solid-fill src and/or mask. Without this
we fallback to sw a lot for common things like text rendering.
Signed-off-by: Rob Clark
---
src/gallium/state_tr
From: Leo Liu
Signed-off-by: Leo Liu
---
src/gallium/drivers/radeon/radeon_vce.c| 22 +++---
src/gallium/drivers/radeon/radeon_vce.h| 3 +++
src/gallium/drivers/radeon/radeon_vce_40_2_2.c | 6 --
3 files changed, 26 insertions(+), 5 deletions(-)
diff --git
https://bugs.freedesktop.org/show_bug.cgi?id=76960
José Fonseca changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On Thu, Apr 3, 2014 at 1:17 AM, Thomas Hellstrom wrote:
> On 04/01/2014 05:04 PM, Rob Clark wrote:
>> From: Rob Clark
>>
>> Add support to property handle solid-fill src and/or mask. Without this
>> we fallback to sw a lot for common things like text rendering.
>>
>> Signed-off-by: Rob Clark
>>
Like AMD_performance_monitor, this extension provides an interface for
applications (and OpenGL-based tools) to access GPU performance
counters. Since the exact performance counters available vary between
vendors and hardware generations, the extension provides an API the
application can use to get
This was marked as somewhere we're deviating from the spec in order to
follow what nVIDIA does. Is there no longer a reason to?
On Thu, Apr 3, 2014 at 7:30 PM, Samuel Iglesias Gonsalvez
wrote:
> According to the spec:
> must be RENDERBUFFER and
> should be set to the name of the
https://bugs.freedesktop.org/show_bug.cgi?id=67672
Vladimír Čunát changed:
What|Removed |Added
Version|9.2 |10.0
--- Comment #20 from Vladimír Čuná
68 matches
Mail list logo
