https://bugs.freedesktop.org/show_bug.cgi?id=62647
--- Comment #23 from Alexandre Derumier ---
Hi, I would like to help,
can somebody tell me how to do traces and debug it? (Sorry I'm noob).
Also I notice that ilo and i965g have the same display bug, do they share
something in common ?
--
Yo
Kenneth Graunke writes:
> The __DRI_USE_INVALIDATE extension was added in May 11th, 2010 by commit
> 4258e3a2e1c327. At this point, it's unlikely that anyone's using the
> right mix of new and old components to hit this path. Deleting it
> removes an untested code path and cleans up the driver
https://bugs.freedesktop.org/show_bug.cgi?id=66423
Alexandre Demers changed:
What|Removed |Added
CC||bri...@vmware.com,
---
src/gallium/drivers/r600/r600_hw_context.c | 5 ++---
src/gallium/drivers/r600/r600_pipe.c | 5 +
src/gallium/drivers/r600/r600_pipe.h | 1 +
3 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/src/gallium/drivers/r600/r600_hw_context.c
b/src/gallium/drivers/r600/r6
It's done automatically for vertex buffers, but not for constant buffers,
textures, and colorbuffers.
---
src/gallium/drivers/r600/r600_blit.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/src/gallium/drivers/r600/r600_blit.c
b/src/gallium/drivers/r600/r600_blit.c
index ba5d4
also flushing any cache in evergreen_emit_cs_shader seems to be superfluous
(we don't flush caches when changing the other shaders either)
---
src/gallium/drivers/r600/evergreen_compute.c| 8 +++
src/gallium/drivers/r600/evergreen_hw_context.c | 8 +--
src/gallium/drivers/r600/r600_h
This should increase performance if constant uploads are done with the CP DMA.
---
src/gallium/drivers/r600/evergreen_hw_context.c | 21 +---
src/gallium/drivers/r600/r600_hw_context.c | 126 +---
src/gallium/drivers/r600/r600_pipe.h| 2 +
3 files changed, 1
---
src/gallium/drivers/r600/r600_blit.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/gallium/drivers/r600/r600_blit.c
b/src/gallium/drivers/r600/r600_blit.c
index 7a0e256..ba5d4ea 100644
--- a/src/gallium/drivers/r600/r600_blit.c
+++ b/src/gallium/drivers/r600/r600
The winsys should do this, because it measures how much time we spend
in buffer_map doing synchronization, which can be viewed with the gallium
HUD.
---
src/gallium/drivers/r600/r600_pipe.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/src/gallium/drivers/r600/r600_pipe.c
From: Alex Deucher
1. flush SH with read caches
2. add flag for DB flushes
3. add flag for CB flushes
v2: flush all CBs, remove redundant emit_state variable.
v3: Marek: also set the new flags in r600_context_flush, the CP dma functions,
and texture_barrier, and rename them
Signed-off-by: A
---
src/gallium/drivers/r600/r600_texture.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/src/gallium/drivers/r600/r600_texture.c
b/src/gallium/drivers/r600/r600_texture.c
index 5ad8c65..36cca17 100644
--- a/src/gallium/drivers/r600/r600_texture.c
+++ b/src/
the winsys does this automatically
---
src/gallium/drivers/r600/r600_texture.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/src/gallium/drivers/r600/r600_texture.c
b/src/gallium/drivers/r600/r600_texture.c
index c2feb52..5ad8c65 100644
--- a/src/gallium/drivers/r600/r600_texture.c
+++
It was wrong, because the offset shouldn't be applied to MSAA depth buffers.
This small cleanup should prevent such issues in the future.
This fixes a lockup in "piglit/fbo-depthstencil default_fb -samples=n".
The lockup was special, because it was triggered by the CPU writing to memory
outside o
---
src/gallium/drivers/r600/r600_blit.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/src/gallium/drivers/r600/r600_blit.c
b/src/gallium/drivers/r600/r600_blit.c
index 3b8a28b..7a0e256 100644
--- a/src/gallium/drivers/r600/r600_blit.c
+++ b/src/gallium/drivers/r600/r
this also fixes the fast clear with multiple colorbuffers and each having
a different format
---
src/gallium/drivers/r600/r600_blit.c | 21 -
1 file changed, 12 insertions(+), 9 deletions(-)
diff --git a/src/gallium/drivers/r600/r600_blit.c
b/src/gallium/drivers/r600/r600_bli
https://bugs.freedesktop.org/show_bug.cgi?id=66423
Alexandre Demers changed:
What|Removed |Added
Hardware|Other |All
--
You are receiving this mail b
https://bugs.freedesktop.org/show_bug.cgi?id=66423
Priority: medium
Bug ID: 66423
Assignee: mesa-dev@lists.freedesktop.org
Summary: [bisected] postprocess/pp_run.c :56:pp_run: Assertion
ppq->tmp[1] failed
Severity: normal
https://bugs.freedesktop.org/show_bug.cgi?id=64692
Marek Olšák changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
See my explanation in mtypes.h.
v2: don't do this in gallium
---
src/glsl/linker.cpp| 16
src/mesa/drivers/dri/i965/brw_shader.cpp | 8 ++--
src/mesa/main/mtypes.h | 8 ++--
src/mesa/main/shaderobj.h | 4 ++
FYI, I have applied the patch to my local branch and added a few more
fixes. I'll send it once I finish some other things I'm working on right
now.
Marek
On Sun, Jun 23, 2013 at 11:56 PM, Alex Deucher wrote:
> On Sun, Jun 23, 2013 at 2:24 PM, Marek Olšák wrote:
>> Hi Alex,
>>
>> rctx->framebuff
- Original Message -
> Brian Paul writes:
>
> > On 06/26/2013 04:33 PM, Eric Anholt wrote:
> >> Brian Paul writes:
> >>
> >>> On 06/26/2013 03:56 PM, Ian Romanick wrote:
> Patches 1 and 4 are
>
> Reviewed-by: Ian Romanick
>
> For patch 3, I share Jose's concer
21 matches
Mail list logo