https://bugs.freedesktop.org/show_bug.cgi?id=50754
Alexandre Demers changed:
What|Removed |Added
Attachment #65690|0 |1
is obsolete|
The easy part is turning on the extension, now that the X server has a patch
to send the events.
The only trick was making sure the Present extension reliably provided the
right 'sbc' count back in the event, and that's done by making sure the sbc
count is always the same as the sequence number th
This allows GL to support the GLX_INTEL_swap_event extension
Signed-off-by: Keith Packard
---
This is the X server side; the mesa patch will be sent shortly (it's tiny)
glx/Makefile.am | 3 ++-
glx/glxcmds.c | 69 +
glx/glxdri2
https://bugs.freedesktop.org/show_bug.cgi?id=50754
--- Comment #24 from Alexandre Demers ---
(In reply to comment #23)
> (In reply to comment #22)
> > I'm closing this bug because I'm able to crosscompile anytime with the help
> > of some variables.
>
> This is Mesa bug. You being able to work
https://bugs.freedesktop.org/show_bug.cgi?id=45466
--- Comment #3 from Alexandre Demers ---
Comment on attachment 56473
--> https://bugs.freedesktop.org/attachment.cgi?id=56473
Improved version of the patch that touches mklib as well
Review of attachment 56473:
On Mit, 2013-11-20 at 15:20 +0100, Marek Olšák wrote:
> From: Marek Olšák
>
> There are also some changes to the printfs.
This series is
Reviewed-and-Tested-by: Michel Dänzer
--
Earthling Michel Dänzer| http://www.amd.com
Libre software enthusiast |
Always nice to clean up after ourselves.
Signed-off-by: Keith Packard
---
v2: Include changes to dri3_priv.h as well
src/glx/dri3_glx.c | 17 -
src/glx/dri3_priv.h | 5 -
2 files changed, 20 insertions(+), 2 deletions(-)
diff --git a/src/glx/dri3_glx.c b/src/glx/dri3_glx
Always nice to clean up after ourselves.
Signed-off-by: Keith Packard
---
Ok, so not having this in the dri3 code led to a bit of extra memory
usage in apps and the X server.
src/glx/dri3_glx.c | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/src/glx/dri3_g
> For me too, other than the fixed_position members, looks good. Thanks for
> your perseverance on this Zack!
Thanks! ok, attached is a version that makes position and dx/dy 32bit again, it
seems to work great. I have a question for you guys if you run the piglits:
./bin/triangle-rasterization-o
https://bugs.freedesktop.org/show_bug.cgi?id=71904
Priority: medium
Bug ID: 71904
Keywords: regression
CC: airl...@freedesktop.org
Assignee: mesa-dev@lists.freedesktop.org
Summary: [swrast] piglit glsl-reload-source regression
https://bugs.freedesktop.org/show_bug.cgi?id=71903
Priority: medium
Bug ID: 71903
Keywords: regression
CC: airl...@freedesktop.org
Assignee: mesa-dev@lists.freedesktop.org
Summary: [swrast] piglit hiz-depth-read-window-stencil0
libxshmfence foolishly advertises the type of a fence as 'int32_t *', which
works when the fence is a linux futex. However, that library is going to
change the exported datatype to 'struct xshmfence *', which will provide some
nice typechecking. Anticipate the change by just using 'void *' in mesa,
Upper levels of the stack use base.stamp to tell when a drawable needs to be
revalidated, but the dri state tracker was using dPriv->lastStamp. Those two,
along with dri2.stamp, all get simultaneously incremented when a dri2
invalidate event was delivered, and so end up containing precisely the sam
The __DRIimage createImageFromFds function takes a fourcc code, but there was
no fourcc code that match __DRI_IMAGE_FORMAT_SARGB8. This adds a define for
that format, adds a translation in DRI3 from __DRI_IMAGE_FORMAT_SARGB8 to
__DRI_IMAGE_FOURCC_SARGB and then adds translations *back* to
__IMA
On 11/19/2013 04:16 PM, Courtney Goeltzenleuchter wrote:
Add helper function to set texture_view state from TexStorage calls.
Signed-off-by: Courtney Goeltzenleuchter
---
src/mesa/main/textureview.c | 59 +
src/mesa/main/textureview.h | 4 +++
2
On 11/19/2013 04:16 PM, Courtney Goeltzenleuchter wrote:
Signed-off-by: Courtney Goeltzenleuchter
---
src/mesa/drivers/common/driverfuncs.c | 3 +++
src/mesa/main/dd.h| 5 +
2 files changed, 8 insertions(+)
diff --git a/src/mesa/drivers/common/driverfuncs.c
b/src/m
On 11/19/2013 04:16 PM, Courtney Goeltzenleuchter wrote:
The following patches add the necessary functions to Mesa
to support ARB_texture_view. These patches do not include
the actual driver elements, just the device independent portion.
This extension requires ARB_texture_storage.
The extension
I'd rename this summary as something like "mesa: implement the
_mesa_TextureView() function"
On 11/19/2013 04:16 PM, Courtney Goeltzenleuchter wrote:
Add Mesa TextureView logic.
Incorporate feedback on ARB_texture_view
Signed-off-by: Courtney Goeltzenleuchter
---
src/mesa/main/textureview.
On Thu, Nov 07, 2013 at 05:13:35PM +0100, Axel Davy wrote:
> These patches enable using DRI_PRIME to use a different card
> than the compositor card (with render-nodes).
>
> At the time of writing, Mesa Wayland egl backend doesn't
> support render-nodes, because it uses the dri2 backend, which
> r
On Thu, Nov 07, 2013 at 05:13:37PM +0100, Axel Davy wrote:
> We must send to the compositor buffer it is able to read.
>
> Since tiling modes are different on graphic cards, we have
> to disable tiling when creating the buffers if we render
> with a different graphic card than the compositor.
>
>
On Thu, Nov 07, 2013 at 05:13:36PM +0100, Axel Davy wrote:
> This patch moves the code to open the graphic device in the Wayland backend,
> removes the authentication request when we are on a render-node,
> and has a few fixes.
>
> Signed-off-by: Axel Davy
> ---
> src/egl/drivers/dri2/egl_dri2.h
On Thu, 2013-11-21 at 14:12 +0100, Thomas Hellstrom wrote:
> On 11/21/2013 05:11 AM, christopher.halse.rog...@canonical.com wrote:
> > From: Christopher James Halse Rogers
> >
> > Otherwise the default is TYPE_SHARED, which will flink the bo. This seems
> > rather unnecessary for a simple stride q
I was just comparing to the list in the ARB_viewport_array spec.
On Fri, Nov 22, 2013 at 11:33 AM, Courtney Goeltzenleuchter <
court...@lunarg.com> wrote:
> Hi Chris,
>
> Where are you getting your defines?
> I copied them from include/GL/gl.h
> #define GL_VIEWPORT 0x0BA2
> /* Scissor box */
> #
On 11/21/2013 10:12 PM, Brian Paul wrote:
And use a better assertion.
---
src/mesa/main/ffvertex_prog.c | 26 ++
1 file changed, 14 insertions(+), 12 deletions(-)
diff --git a/src/mesa/main/ffvertex_prog.c b/src/mesa/main/ffvertex_prog.c
index be6ac0f..074fbf9 100644
I sent one suggestion on patch 1.
Series: Reviewed-by: Jordan Justen
On Wed, Nov 20, 2013 at 2:29 PM, Paul Berry wrote:
> From section 4.4.7 (Layered Framebuffers) of the GLSL 3.2 spec:
>
> When the Clear or ClearBuffer* commands are used to clear a
> layered framebuffer attachment, all
Hi Chris,
Where are you getting your defines?
I copied them from include/GL/gl.h
#define GL_VIEWPORT 0x0BA2
/* Scissor box */
#define GL_SCISSOR_BOX 0x0C10
#define GL_SCISSOR_TEST 0x0C11
#define GL_SCISSOR_TEST 0x0C11
#define GL_DEPTH_RANGE 0x0B70
Ah, FIRST_VERTEX looks different.
#define GL_FIRS
On Wed, 2013-11-20 at 14:29 -0800, Paul Berry wrote:
> In order to properly clear layered framebuffers, we need to know how
> many layers they have. The easiest way to do this is to record it in
> the gl_framebuffer struct when we check framebuffer completeness.
>
> This patch replaces the gl_fra
And use a better assertion.
---
src/mesa/main/ffvertex_prog.c | 26 ++
1 file changed, 14 insertions(+), 12 deletions(-)
diff --git a/src/mesa/main/ffvertex_prog.c b/src/mesa/main/ffvertex_prog.c
index be6ac0f..074fbf9 100644
--- a/src/mesa/main/ffvertex_prog.c
+++ b/src
---
src/mesa/state_tracker/st_mesa_to_tgsi.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/mesa/state_tracker/st_mesa_to_tgsi.c
b/src/mesa/state_tracker/st_mesa_to_tgsi.c
index 7d79c62..1c2abc1 100644
--- a/src/mesa/state_tracker/st_mesa_to_tgsi.c
+++ b/src/mesa/state
Useful for finding the associated control flow instructions, given a
block ending in one.
---
v2: Handle nested control flow properly. When we reach the ENDIF, we have
still have the pointers to the IF and ELSE (if it exists).
The confusing bit of this code is that while bblock_t *cur_if i
On 11/21/2013 07:01 AM, jfons...@vmware.com wrote:
From: José Fonseca
These degenerate instructions can often be emitted by state trackers
when the semantics of instructions don't match precisely.
---
src/gallium/auxiliary/tgsi/tgsi_ureg.c | 8
src/gallium/auxiliary/tgsi/tgsi_ureg.
I'm surprised the build system accepts the conflicting second definition of
SCISSOR_BOX at all, actually -- that's weird.
On Fri, Nov 22, 2013 at 8:55 AM, Chris Forbes wrote:
> I mean some of the values don't match the spec :)
>
>
> On Fri, Nov 22, 2013 at 7:52 AM, Courtney Goeltzenleuchter <
>
I currently work on a simpler solution for Gallium. I'm using
AMD_vertex_shader_layer and this vertex shader (I wrote it in TGSI
though):
void main()
{
gl_Position = gl_Vertex;
gl_TexCoord[0] = MultiTexCoord0; // clear color
gl_Layer = gl_InstanceID;
}
Then I render the quad with Draw
Hello,
just recently I encountered a problem when linking shaders, containing
uniform consisting of anonymous structure.
Here is the code of shaders, triggering the problem:
//vertex shader
uniform struct {vec3 a; vec3 b;} a;
void main()
{
gl_Position = gl_ModelViewProjectionMatrix * gl_Vertex;
From: José Fonseca
Mere syntactical change.
---
src/gallium/auxiliary/tgsi/tgsi_ureg.h | 200 +
1 file changed, 104 insertions(+), 96 deletions(-)
diff --git a/src/gallium/auxiliary/tgsi/tgsi_ureg.h
b/src/gallium/auxiliary/tgsi/tgsi_ureg.h
index e104cd9..cf0c75e
On 11/21/2013 05:11 AM, christopher.halse.rog...@canonical.com wrote:
Now includes support for Image 6 as a bonus feature, and 7 is only exposed
on the gallium drivers which support dma-buf import/export.
Still useful for Wayland-Prime and Mir, now also useful for DRI3000
__
On 11/21/2013 05:11 AM, christopher.halse.rog...@canonical.com wrote:
From: Christopher James Halse Rogers
Otherwise the default is TYPE_SHARED, which will flink the bo. This seems
rather unnecessary for a simple stride query.
Is there no way we can cache this stuff in a __DRIimage? Changing
Eric Anholt writes:
> Paul Berry writes:
>
>> From section 4.4.7 (Layered Framebuffers) of the GLSL 3.2 spec:
>>
>> When the Clear or ClearBuffer* commands are used to clear a
>> layered framebuffer attachment, all layers of the attachment are
>> cleared.
>>
>> This patch fixes meta
I mean some of the values don't match the spec :)
On Fri, Nov 22, 2013 at 7:52 AM, Courtney Goeltzenleuchter <
court...@lunarg.com> wrote:
>
>
> On Wed, Nov 20, 2013 at 7:28 PM, Chris Forbes wrote:
>
>> Oops -- the 8E4E is obviously correct. Artifact of me switching how I
>> was commenting half
On 21 November 2013 05:21, Marek Olšák wrote:
> I currently work on a simpler solution for Gallium. I'm using
> AMD_vertex_shader_layer and this vertex shader (I wrote it in TGSI
> though):
>
> void main()
> {
> gl_Position = gl_Vertex;
> gl_TexCoord[0] = MultiTexCoord0; // clear color
>
The patch looks fine, but I'm not sure I understand the comment with
respect to the code change. I'd probably just call it something like
"tgsi: rework calls to ureg_emit_insn()"
But not a big deal.
Reviewed-by: Brian Paul
On 11/21/2013 07:01 AM, jfons...@vmware.com wrote:
From: José Fons
- Original Message -
> Great!
>
> Couple of comments inline.
>
> On 11/21/2013 12:02 AM, Zack Rusin wrote:
> > 8 bit precision is required by d3d10 but unfortunately
> > requires 64 bit rasterizer. This commit implements
> > 64 bit rasterization with full support for 8bit subpixel
> > pre
On 11/21/2013 02:01 PM, jfons...@vmware.com wrote:
From: José Fonseca
These degenerate instructions can often be emitted by state trackers
when the semantics of instructions don't match precisely.
---
src/gallium/auxiliary/tgsi/tgsi_ureg.c | 8
src/gallium/auxiliary/tgsi/tgsi_ureg.
On Wed, Nov 20, 2013 at 7:28 PM, Chris Forbes wrote:
> Oops -- the 8E4E is obviously correct. Artifact of me switching how I
> was commenting halfway through.
>
> On Thu, Nov 21, 2013 at 3:25 PM, Chris Forbes wrote:
> > These are bogus:
> >
> > +
> > +
> > +
> > +
> > +
>
Wh
https://bugs.freedesktop.org/show_bug.cgi?id=71591
--- Comment #6 from Eero Tamminen ---
Giving an error when the extension changes behavior of existing functionality
can be useful for developers, as such things may cause grief for them. For
anything else, it's the error itself that causes grief
From: José Fonseca
These degenerate instructions can often be emitted by state trackers
when the semantics of instructions don't match precisely.
---
src/gallium/auxiliary/tgsi/tgsi_ureg.c | 8
src/gallium/auxiliary/tgsi/tgsi_ureg.h | 22 ++
2 files changed, 30 inse
On 11/21/2013 06:03 PM, jfons...@vmware.com wrote:
From: José Fonseca
Several links contributed by Keith Whitwell and Roland Scheidegger.
---
docs/llvmpipe.html | 58 --
1 file changed, 56 insertions(+), 2 deletions(-)
diff --git a/docs/ll
Considering you're the only user of meta_clear who cares about it,
it's all up to you. If your hardware can do AMD_vertex_shader_layer,
you won't ever have to implement any other code path.
It's silly to have multiple GLSL shaders for different versions of the
API. I think this should be API-indep
From: José Fonseca
Several links contributed by Keith Whitwell and Roland Scheidegger.
---
docs/llvmpipe.html | 58 --
1 file changed, 56 insertions(+), 2 deletions(-)
diff --git a/docs/llvmpipe.html b/docs/llvmpipe.html
index 80f8a01..d695907
Paul Berry writes:
> From section 4.4.7 (Layered Framebuffers) of the GLSL 3.2 spec:
>
> When the Clear or ClearBuffer* commands are used to clear a
> layered framebuffer attachment, all layers of the attachment are
> cleared.
>
> This patch fixes meta clears to properly clear all lay
On 11/21/2013 11:03 AM, jfons...@vmware.com wrote:
From: José Fonseca
Several links contributed by Keith Whitwell and Roland Scheidegger.
---
Nice.
Reviewed-by: Brian Paul
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.free
Great!
Couple of comments inline.
On 11/21/2013 12:02 AM, Zack Rusin wrote:
8 bit precision is required by d3d10 but unfortunately
requires 64 bit rasterizer. This commit implements
64 bit rasterization with full support for 8bit subpixel
precision. It's a combination of all individual commits
https://bugs.freedesktop.org/show_bug.cgi?id=41700
Bug 41700 depends on bug 50754, which changed state.
Bug 50754 Summary: Building 32 bit mesa on 64 bit OS fails since change for
automake
https://bugs.freedesktop.org/show_bug.cgi?id=50754
What|Removed |Added
https://bugs.freedesktop.org/show_bug.cgi?id=45466
Bug 45466 depends on bug 50754, which changed state.
Bug 50754 Summary: Building 32 bit mesa on 64 bit OS fails since change for
automake
https://bugs.freedesktop.org/show_bug.cgi?id=50754
What|Removed |Added
https://bugs.freedesktop.org/show_bug.cgi?id=50754
Eero Tamminen changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
On 10/23/2013 01:41 AM, Jørgen Lind wrote:
> ---
> src/egl/drivers/dri2/egl_dri2.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/src/egl/drivers/dri2/egl_dri2.c b/src/egl/drivers/dri2/egl_dri2.c
> index b29eb1c..b143a95 100644
> --- a/src/egl/drivers/dri2/egl_dri2.c
> +++ b/src/egl/d
On 10/24/2013 12:13 PM, Courtney Goeltzenleuchter wrote:
> If a user set MESA_INFO and the OpenGL application uses a
> 3.0 or later context then the MESA_INFO debug output will have
> an error when it queries for extensions using the deprecated
> enum GL_EXTENSIONS. Passing context argument allows
On 11/21/2013 05:11 AM, christopher.halse.rog...@canonical.com wrote:
From: Thomas Hellstrom
This needs a prime-aware vmwgfx kernel module to work properly.
(With additions by Christopher James Halse Rogers )
Signed-off-by: Thomas Hellstrom
---
src/gallium/targets/dri-vmwgfx/target.c
On 11/20/2013 02:10 PM, Chad Versace wrote:
> This series makes clamp_max_samples actually useful enabling/disabling MSAA on
> Chromium. Without this series, clamp_max_samples=0 makes WebGL context
> creation
> fail on Chromium.
>
> Eric complained that brw_clamp_max_samples() too closely resembl
59 matches
Mail list logo
