Signed-off-by: Ilia Mirkin
---
src/gallium/drivers/vc4/vc4_screen.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gallium/drivers/vc4/vc4_screen.c
b/src/gallium/drivers/vc4/vc4_screen.c
index 84aae91..43742c9 100644
--- a/src/gallium/drivers/vc4/vc4_screen.c
+++ b/src/g
Previously glx was using the xcb connection from Xlib.
It is a problem because there are issues if Xlib is used
in another thread (Present event lost)
This patch creates a per-context xcb connection to solve this issue.
Solves: https://bugs.freedesktop.org/show_bug.cgi?id=84252
Tested-by: Tobias
On Sat, Apr 18, 2015 at 1:55 PM, Kenneth Graunke wrote:
> On Friday, April 17, 2015 07:12:00 PM Jason Ekstrand wrote:
>> ---
>> src/mesa/drivers/dri/i965/brw_fs_generator.cpp | 11 ++-
>> src/mesa/drivers/dri/i965/brw_shader.cpp | 13 +
>> src/mesa/drivers/dri/i965/b
On Friday, April 17, 2015 07:12:00 PM Jason Ekstrand wrote:
> ---
> src/mesa/drivers/dri/i965/brw_fs_generator.cpp | 11 ++-
> src/mesa/drivers/dri/i965/brw_shader.cpp | 13 +
> src/mesa/drivers/dri/i965/brw_shader.h | 2 ++
> src/mesa/drivers/dri/i965/brw_
Ah I totally missed that it's queryable!
So I guess this is a test bug then.
(Interestingly, the spec doesn't quite tell what happens in the case if
a buffer's size isn't sufficiently aligned - if the offset is not
sufficiently aligned an error is generated but not if the size isn't.
The state tabl
On Fri, Apr 17, 2015 at 1:21 PM, Timothy Arceri wrote:
> Hi all,
>
> Last year I spent a whole bunch of time profiling Mesa looking for areas
> where improvements could be made. Anyway I thought I'd point out a
> couple of things, and see if anyone thinks these are worthwhile
> following up.
>
> 1
Hi Roland,
GL_UNIFORM_BUFFER_OFFSET_ALIGNMENT or
PIPE_CAP_CONSTANT_BUFFER_OFFSET_ALIGNMENT is what you're looking for.
I guess the test shouldn't ignore that. The value is 256 for R600 and
4 for GCN.
Marek
On Sat, Apr 18, 2015 at 5:46 AM, Roland Scheidegger wrote:
> Hi,
>
> when looking at a re
Previously glx was using the xcb connection from Xlib.
It is a problem for several reasons:
. There are issues if Xlib is used in another thread (Present event lost)
. Mixing Present events if you receive some for different windows (ie
the client is having more than one window it renders to)
This
