Hi Tom,
First I'd like to say that even though I don't agree with the
direction you're taking, I'd be okay with it for initial bring-up of
the compute support.
I am not in favor of using radeon_surface for plain untyped 1D
buffers, where the only thing that really matters is the buffer
alignment,
v2: fix off-by-one error in is_box_inside_resource, add comments
---
src/gallium/auxiliary/util/u_blitter.c | 140
src/gallium/auxiliary/util/u_blitter.h | 12 +++
2 files changed, 152 insertions(+)
diff --git a/src/gallium/auxiliary/util/u_blitter.c
b/src/gal
On 09/12/2012 08:51 PM, Paul Berry wrote:
> This patch is a band-aid fix for a bug in commit 5fd67fa (i965/blorp:
> Reduce alignment restrictions for stencil blits), which causes
> multisampled stencil blits to work incorrectly on Sandy Bridge.
>
> When blitting to or from a normal stencil buffer,
Haswell supports EXT_texture_swizzle and legacy DEPTH_TEXTURE_MODE
swizzling by setting SURFACE_STATE entries. This means we don't have to
bake the swizzle settings into the shader code by emitting MOV
instructions, and thus don't have to recompile shaders whenever the
swizzles change.
Unfortunat
It's going to be reused in a second place soon.
Cc: Paul Berry
Signed-off-by: Kenneth Graunke
---
src/mesa/drivers/dri/i965/brw_state.h| 2 +
src/mesa/drivers/dri/i965/brw_wm.c | 51 +
src/mesa/drivers/dri/i965/brw_wm_surface_state.c | 56 +
>From SandyBridge PRM, volume 2 Part 1, section 12.2.3, BLEND_STATE:
DWord 1, Bit 30 (AlphaToOne Enable):
"If Dual Source Blending is enabled, this bit must be disabled"
Signed-off-by: Anuj Phogat
---
src/mesa/drivers/dri/i965/gen6_cc.c | 13 +++--
1 files changed, 11 insertions(+), 2
On Fri, Sep 21, 2012 at 3:11 AM, Eric Anholt wrote:
> The only symbols that need to be public (those in intel_screen.c that the
> loader looks for) are already marked public. Saves 100k of compiled driver
> size.
> ---
> src/mesa/drivers/dri/i965/Makefile.am |1 +
> 1 file changed, 1 inserti
From: Tom Stellard
---
src/gallium/state_trackers/clover/api/device.cpp | 5 -
src/gallium/state_trackers/clover/core/device.cpp | 6 ++
src/gallium/state_trackers/clover/core/device.hpp | 1 +
3 files changed, 11 insertions(+), 1 deletion(-)
diff --git a/src/gallium/state_trackers/clo
From: Tom Stellard
---
src/gallium/drivers/r600/r600_pipe.c | 10 ++
src/gallium/include/pipe/p_defines.h | 3 ++-
2 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/src/gallium/drivers/r600/r600_pipe.c
b/src/gallium/drivers/r600/r600_pipe.c
index 658e9a9..55db78c 100644
--
From: Tom Stellard
v2:
- Use pc parameter of launch_grid
---
src/gallium/drivers/r600/evergreen_compute.c | 42 ++
.../drivers/r600/evergreen_compute_internal.h | 18 ++
src/gallium/drivers/r600/llvm_wrapper.cpp | 38
src/gal
From: Tom Stellard
---
src/gallium/state_trackers/clover/api/kernel.cpp | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/src/gallium/state_trackers/clover/api/kernel.cpp
b/src/gallium/state_trackers/clover/api/kernel.cpp
index ab4982d..6ef2b05 100644
--- a/src/g
From: Blaž Tomažič
v2: Tom Stellard
- Use pc parameter of launch_grid()
---
src/gallium/include/pipe/p_context.h | 4 ++
.../state_trackers/clover/llvm/invocation.cpp | 66 +++---
2 files changed, 37 insertions(+), 33 deletions(-)
diff --git a/src/gallium/i
From: Tom Stellard
---
src/gallium/drivers/r600/compute_memory_pool.c | 15 +--
src/gallium/drivers/r600/r600_pipe.c | 7 +++
2 files changed, 4 insertions(+), 18 deletions(-)
diff --git a/src/gallium/drivers/r600/compute_memory_pool.c
b/src/gallium/drivers/r600/comp
From: Tom Stellard
The items are ordered in the item list by their offsets, with the lowest
offset coming first in the list. The old code was assuming that new
items being added to the list would always have a greater offset than
the first item in the list, however this is not always the case.
-
From: Tom Stellard
---
src/gallium/drivers/r600/compute_memory_pool.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/src/gallium/drivers/r600/compute_memory_pool.c
b/src/gallium/drivers/r600/compute_memory_pool.c
index 5e25a1d..9404f0a 100644
--- a/src/gallium/driver
From: Tom Stellard
---
src/gallium/drivers/r600/compute_memory_pool.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gallium/drivers/r600/compute_memory_pool.c
b/src/gallium/drivers/r600/compute_memory_pool.c
index bd3c14d..5e25a1d 100644
--- a/src/gallium/drivers/r600/
From: Tom Stellard
This function creates a buffer with an associated radeon_surface that
can be used as a RAT.
---
src/gallium/drivers/r600/r600_buffer.c | 69
src/gallium/drivers/r600/r600_pipe.h | 2 +
src/gallium/drivers/r600/r600_resource.h | 5 +++
s
From: Tom Stellard
---
This change needs the drm patch I sent to the list in order to work:
radeon: Allow N x 1 x 1 surfaces for evergreen+
src/gallium/drivers/r600/r600_texture.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gallium/drivers/r600/r600_texture.c
b/sr
Hi,
These series improves how the r600g compute code uses buffers for
global memory. I'm interested in getting some feedback on these,
especially patches 1 and 2.
Thanks,
Tom
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freede
On Mon, Sep 17, 2012 at 8:22 AM, Andreas Boll
wrote:
> Yep, vdpau is also affected.
>
> $ LD_LIBRARY_PATH="/home/andreas/mesa-testing/lib/vdpau"
> VDPAU_DRIVER=r600' vdpauinfo
> display: :0 screen: 0
> Failed to open VDPAU backend
> /home/andreas/mesa-testing/lib/vdpau/libvdpau_r600.so: undefine
On 09/14/2012 11:09 AM, Marek Olšák wrote:
This series reworks blitting and MSAA resolving in Gallium as discussed here:
http://www.mail-archive.com/mesa-dev@lists.freedesktop.org/msg26592.html
I'd like to clarify some more rules for the blit function:
- Z/S blitting must always be supported reg
On 09/14/2012 11:09 AM, Marek Olšák wrote:
---
src/gallium/drivers/i915/i915_screen.c |1 +
src/gallium/drivers/llvmpipe/lp_screen.c |1 +
src/gallium/drivers/nv30/nv30_screen.c |1 +
src/gallium/drivers/nv50/nv50_screen.c |1 +
src/gallium/drivers/nvc0/nvc0_screen.c
On 09/14/2012 11:09 AM, Marek Olšák wrote:
---
src/gallium/auxiliary/util/u_blitter.c | 136
src/gallium/auxiliary/util/u_blitter.h |4 +
2 files changed, 140 insertions(+)
diff --git a/src/gallium/auxiliary/util/u_blitter.c
b/src/gallium/auxiliary/util
On 09/20/2012 04:19 PM, Anuj Phogat wrote:
A call to glGenerateMipmap() follows the generation of a relevant
shader program in setup_glsl_generate_mipmap().
To support all texture targets and to avoid compiling shaders
everytime, per target shader programs are compiled on demand
and saved for th
On 09/20/2012 09:59 AM, Robert Bragg wrote:
This adds an egl_probe_front_pixel_rgb function that is analogous to
piglit_probe_pixel_rgba except it probes the front buffer instead of
probing the back buffer.
---
tests/egl/egl-util.c | 31 +++
tests/egl/egl-util.h |
On Tue, Sep 18, 2012 at 10:57:22PM +0200, Vincent Lejeune wrote:
Reviewed-by: Tom Stellard
This patch is OK to commit if there are no regressions with the LLVM
compiler.
> ---
> src/gallium/drivers/radeon/AMDGPUISelLowering.cpp | 2 +
> src/gallium/drivers/radeon/AMDGPUISelLowering.h|
Fixes divide by zero issue in llvmpipe driver.
---
src/mesa/state_tracker/st_cb_texture.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/src/mesa/state_tracker/st_cb_texture.c
b/src/mesa/state_tracker/st_cb_texture.c
index 4f4fe77..5634a3e 100644
--- a/src/mesa/state
Tom Stellard writes:
> From: Tom Stellard
>
> ---
> src/gallium/state_trackers/clover/api/device.cpp | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/src/gallium/state_trackers/clover/api/device.cpp
> b/src/gallium/state_trackers/clover/api/device.cpp
> index 1a9127b.
Tom Stellard writes:
> From: Tom Stellard
>
Thanks, Reviewed-by: Francisco Jerez
> ---
> src/gallium/state_trackers/clover/api/transfer.cpp | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/gallium/state_trackers/clover/api/transfer.cpp
> b/src/gallium/state_tracke
Tom Stellard writes:
> From: Tom Stellard
>
> On debug builds these were always being printed.
> ---
>
> Are these printfs useful to anyone? Should they be controlled with an
> ENV variable instead?
>
Not much I guess... Reviewed-by: Francisco Jerez
> src/gallium/auxiliary/pipe-loader/pipe_l
On 09/21/2012 03:11 AM, Eric Anholt wrote:
> ---
> src/mesa/drivers/dri/i965/brw_vs_emit.c | 83
> ---
> 1 file changed, 83 deletions(-)
And good riddance!
For the series:
Reviewed-by: Kenneth Graunke
___
mesa-dev maili
Hello;
On 09/20/2012 11:01 PM, Chad Versace wrote:
> Adding Tapani to the CC list. Removing Oliver.
>
> On 09/20/2012 09:55 PM, Chad Versace wrote:
>> Fixes valgrind errors in piglit test
>> oes_compressed_etc1_rgb8_texture-miptree: an invalid write in
>> _mesa_store_compressed_store_texsubimage(
This was for some of the old spans-related code that is now gone.
---
src/mesa/drivers/dri/intel/intel_tex.h|2 -
src/mesa/drivers/dri/intel/intel_tex_format.c | 50 -
2 files changed, 52 deletions(-)
diff --git a/src/mesa/drivers/dri/intel/intel_tex.h
b/src
---
src/mesa/drivers/dri/i965/brw_shader.cpp |2 +-
src/mesa/drivers/dri/i965/brw_state.h |5 -
src/mesa/drivers/dri/i965/brw_state_upload.c |2 +-
src/mesa/drivers/dri/i965/gen7_wm_surface_state.c |2 +-
src/mesa/drivers/dri/intel/intel_batchbuffer.c
---
src/mesa/drivers/dri/i965/brw_disasm.c | 99 ++--
1 file changed, 43 insertions(+), 56 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_disasm.c
b/src/mesa/drivers/dri/i965/brw_disasm.c
index aebfa73..c726ebd 100644
--- a/src/mesa/drivers/dri/i965/brw_dis
The only symbols that need to be public (those in intel_screen.c that the
loader looks for) are already marked public. Saves 100k of compiled driver
size.
---
src/mesa/drivers/dri/i965/Makefile.am |1 +
1 file changed, 1 insertion(+)
diff --git a/src/mesa/drivers/dri/i965/Makefile.am
b/src/
---
src/mesa/drivers/dri/i965/brw_vs_emit.c | 86 ---
1 file changed, 86 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_vs_emit.c
b/src/mesa/drivers/dri/i965/brw_vs_emit.c
index a4c4943..558a1df 100644
--- a/src/mesa/drivers/dri/i965/brw_vs_emit.c
+++ b/src
It's prohibited by ARB_vp and NV_vp, and not used by fixed function t&l.
---
src/mesa/drivers/dri/i965/brw_vs.h |1 -
src/mesa/drivers/dri/i965/brw_vs_emit.c | 67 ++-
2 files changed, 4 insertions(+), 64 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/b
---
src/mesa/drivers/dri/i965/brw_vs_emit.c | 83 ---
1 file changed, 83 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_vs_emit.c
b/src/mesa/drivers/dri/i965/brw_vs_emit.c
index 46954bc..b2b59bc 100644
--- a/src/mesa/drivers/dri/i965/brw_vs_emit.c
+++ b/src
This was added for GLSL support back in the day. It's prohibited by both
ARB_vp and NV_vp.
---
src/mesa/drivers/dri/i965/brw_vs_emit.c | 90 +++
1 file changed, 7 insertions(+), 83 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_vs_emit.c
b/src/mesa/drivers
On 09/21/2012 10:29 AM, Kenneth Graunke wrote:
On 09/21/2012 12:59 AM, Eric Anholt wrote:
This failed when all the uploads to occur were uniform-type vertex data (like
glColor4f being active across a DrawArrays), because it would upload 1 element
instead of 1 element per vertex. There was no ci
Chad Versace writes:
> Fixes valgrind errors in piglit test
> oes_compressed_etc1_rgb8_texture-miptree: an invalid write in
> _mesa_store_compressed_store_texsubimage() at line 4406 and invalid reads
> in texcompress_etc_tmp.h:etc1_parse_block().
>
> The calculation of the size of the temporary e
On Sun, Aug 12, 2012 at 03:50:16PM +0200, Luc Verhaegen wrote:
> Hi,
>
> The FOSDEM organizers have sent out a call for devrooms. FOSDEM this
> year is on the weekend of the 2nd and 3rd of February 2013.
>
> After the success of this formula last year, where, for the first time
> ever, we had a
Chad Versace writes:
> This patch reduces the time spent in glTexImage and glTexSubImage by
> over 5x on Sandybridge for the workload described below.
>
> It adds a new fast path for glTexImage2D and glTexSubImage2D,
> intel_texsubimage_tiled_memcpy, which is optimized for Google Chrome's
> paint
On 09/21/2012 12:59 AM, Eric Anholt wrote:
> This failed when all the uploads to occur were uniform-type vertex data (like
> glColor4f being active across a DrawArrays), because it would upload 1 element
> instead of 1 element per vertex. There was no citation for how this code
> helped any partic
---
src/mesa/drivers/dri/i965/brw_draw_upload.c |4
1 file changed, 4 insertions(+)
diff --git a/src/mesa/drivers/dri/i965/brw_draw_upload.c
b/src/mesa/drivers/dri/i965/brw_draw_upload.c
index 31e092e..f5f65ca 100644
--- a/src/mesa/drivers/dri/i965/brw_draw_upload.c
+++ b/src/mesa/drive
It gets built in Mesa core before we're called these days.
---
src/mesa/drivers/dri/i965/brw_draw.c |7 ---
1 file changed, 7 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_draw.c
b/src/mesa/drivers/dri/i965/brw_draw.c
index a09f555..21abfbe 100644
--- a/src/mesa/drivers/dri/i96
This failed when all the uploads to occur were uniform-type vertex data (like
glColor4f being active across a DrawArrays), because it would upload 1 element
instead of 1 element per vertex. There was no citation for how this code
helped any particular application, and it breaks ETQW, so just remov
Kenneth Graunke writes:
> Given that it exists between a push/pop of instruction state, this call
> can only affect the MOV or ADD instruction generated just below it.
> Neither of those instructions are predicated, so it makes no sense to
> ask for the inverse predicate.
>
> This fixes grumbling
49 matches
Mail list logo