Kenneth Graunke writes:
> Only Gen4 color write setup uses the force_sechalf flag, and it only
> sets it on a single instruction. It also already has to get a pointer
> to the instruction and manually set the saturate flag, so we may as well
> just set force_sechalf the same way and avoid the co
Paul Berry writes:
> When analyzing a loop where the loop condition is expressed in the
> non-standard order (e.g. "4 > i" instead of "i < 4"), we were
> reversing the condition incorrectly, leading to a loop bound that was
> off by 1.
>
> Fixes piglit tests {vs,fs}-loop-bounds-unrolled.shader_te
>>> -Original Message-
>>> From: Ian Romanick [mailto:i...@freedesktop.org]
>>> Sent: Monday, January 07, 2013 7:48 PM
>>> To: Jorge Ramirez Ortiz, HCL Europe
>>> Cc: Dan Nicholson; mesa-dev@lists.freedesktop.org
>>> Subject: Re: [Mesa-dev] glxinfo proposed change
>>>
>>> On 01/07/2013 06:
On Mon, Jan 7, 2013 at 11:18 PM, Matt Turner wrote:
> On Mon, Jan 7, 2013 at 8:16 AM, Anuj Phogat wrote:
>> This patch fixes a case when blitting to a framebuffer with
>> renderbuffers/textures attached to GL_COLOR_ATTACHMENT{1, 2, ...}.
>> Earlier we were incorrectly blitting to GL_COLOR_ATTACHM
On 12/19/2012 04:14 PM, Ian Romanick wrote:
GL_ARB_get_program_binary is a required part of OpenGL ES 3.0, and this
series impelments it for all Mesa drivers. We take the same approach of
implementing the interface with zero binary formats that we take with
GL_ARB_get_shader_binary / OpenGL ES 2
On Mon, Jan 7, 2013 at 6:23 PM, Paul Berry wrote:
> When analyzing a loop where the loop condition is expressed in the
> non-standard order (e.g. "4 > i" instead of "i < 4"), we were
> reversing the condition incorrectly, leading to a loop bound that was
> off by 1.
>
> Fixes piglit tests {vs,fs}-
On 01/07/2013 06:23 PM, Paul Berry wrote:
When analyzing a loop where the loop condition is expressed in the
non-standard order (e.g. "4 > i" instead of "i < 4"), we were
reversing the condition incorrectly, leading to a loop bound that was
off by 1.
Fixes piglit tests {vs,fs}-loop-bounds-unroll
When analyzing a loop where the loop condition is expressed in the
non-standard order (e.g. "4 > i" instead of "i < 4"), we were
reversing the condition incorrectly, leading to a loop bound that was
off by 1.
Fixes piglit tests {vs,fs}-loop-bounds-unrolled.shader_test.
---
src/glsl/loop_controls.
Ian Romanick writes:
> I made fairly substantive changes to patch 4, so I wanted to resend the
> series. Based on discussions in the ARB, we decided that the
> NUM_SAMPLE_COUNTS query in this extension should behave the same way as
> in the GL_ARB_internalformat_query2 extension. The change is
On 01/07/2013 01:08 PM, Jorge Ramirez Ortiz, HCL Europe wrote:
-Original Message-
From: Ian Romanick [mailto:i...@freedesktop.org]
Sent: Monday, January 07, 2013 7:48 PM
To: Jorge Ramirez Ortiz, HCL Europe
Cc: Dan Nicholson; mesa-dev@lists.freedesktop.org
Subject: Re: [Mesa-dev] glxinf
On 01/07/2013 08:16 AM, Anuj Phogat wrote:
These patches are based on gles3 branch of mesa. They were circulated
through the list in last week of Jan. After that I've made few changes
based on suggestions from Ian, ken and Brian. All patches collectively
fix 17 failing test cases in gles3 conform
From: Anuj Phogat
V2:
If mask has GL_STENCIL_BUFFER_BIT set, the depth formats for readRenderBuffer
and drawRenderBuffer must match unless one of the two buffers doesn't have
depth, in which case it's not blitted, so the format check should be ignored.
Same comment goes for stencil formats in dep
On 01/07/2013 08:16 AM, Anuj Phogat wrote:
Changes in fbobject.c fix a case when blitting to a framebuffer with
renderbuffers/textures attached to GL_COLOR_ATTACHMENT{i} (where i!=0).
Earlier it skips color blitting if nothing is found attached to
GL_COLOR_ATTACHMENT0.
Could you please split th
On 01/07/2013 02:34 PM, Matt Turner wrote:
On Mon, Jan 7, 2013 at 1:08 PM, Jorge Ramirez Ortiz, HCL Europe
wrote:
You are absolutely wrong. NULL is a valid return value. Please read the code.
I'm not sure if you missed Ian's point or you're just being pedantic,
but let me try to explain. Th
On Mon, Jan 7, 2013 at 1:08 PM, Jorge Ramirez Ortiz, HCL Europe
wrote:
> You are absolutely wrong. NULL is a valid return value. Please read the code.
I'm not sure if you missed Ian's point or you're just being pedantic,
but let me try to explain. The glxinfo code does this:
if (glXMakeCurrent(
Sounds good to me, especially since it's trivial to do. I'll roll this
into the next version of the series.
-- Chris
On Tue, Jan 8, 2013 at 11:02 AM, Paul Berry wrote:
> On 4 January 2013 13:04, Paul Berry wrote:
>>
>> On 29 December 2012 04:35, Chris Forbes wrote:
>>>
>>> Moves the definition
On 4 January 2013 13:04, Paul Berry wrote:
> On 29 December 2012 04:35, Chris Forbes wrote:
>
>> Moves the definition of the sample locations out of
>> gen6_emit_3dstate_multisample, and unpacks them in
>> gen6_get_sample_postiion.
>>
>> Signed-off-by: Chris Forbes
>> ---
>> src/mesa/drivers/d
Ian Romanick writes:
> On 12/20/2012 05:05 PM, Eric Anholt wrote:
>> Ian Romanick writes:
>>
>>> From: Ian Romanick
>>
>> It looks to me like we really do have to support getting a
>> binary with this extension/gles3:
>>
>> "Any program binary retrieved using GetProgramBinary and submitted us-
Kenneth Graunke writes:
> diff --git a/src/mesa/drivers/dri/i965/brw_vs.c
> b/src/mesa/drivers/dri/i965/brw_vs.c
> index fc57f8a..0a20055 100644
> --- a/src/mesa/drivers/dri/i965/brw_vs.c
> +++ b/src/mesa/drivers/dri/i965/brw_vs.c
> @@ -440,33 +440,38 @@ static void brw_upload_vs_prog(struct brw_
Kenneth Graunke writes:
> diff --git a/src/mesa/drivers/dri/i965/brw_fs_emit.cpp
> b/src/mesa/drivers/dri/i965/brw_fs_emit.cpp
> index 63f09fe..0c2b696 100644
> --- a/src/mesa/drivers/dri/i965/brw_fs_emit.cpp
> +++ b/src/mesa/drivers/dri/i965/brw_fs_emit.cpp
> @@ -387,8 +387,11 @@ fs_generator::g
Patches 2, 3, 4, 7, 8, 13, 22 and 23 are, as-is,
Reviewed-by: Ian Romanick
I still have comments coming for 15 and 17, but I need to do a bit more
research first.
On 01/04/2013 06:41 PM, Jordan Justen wrote:
v1:
* various 2101010 texture tweaks
* integer/signed-int/unsigned-int texture
On 01/04/2013 06:41 PM, Jordan Justen wrote:
Signed-off-by: Jordan Justen
---
src/mesa/main/texstore.c | 21 ++---
1 file changed, 6 insertions(+), 15 deletions(-)
diff --git a/src/mesa/main/texstore.c b/src/mesa/main/texstore.c
index 7511509..6627cf5 100644
--- a/src/mesa/
Previously this was happening unconditionally, leading to some excessive
rebuilding/relinking during builds.
Note that the .po files are not automatically updated due to changes to the
t_options.h file. Instead, translators should continue to use "make po"
manually. This is because after new strin
On 01/04/2013 06:41 PM, Jordan Justen wrote:
Signed-off-by: Jordan Justen
---
src/mesa/drivers/dri/intel/intel_tex_image.c |1 +
1 file changed, 1 insertion(+)
diff --git a/src/mesa/drivers/dri/intel/intel_tex_image.c
b/src/mesa/drivers/dri/intel/intel_tex_image.c
index 9676623..c6bb0f2
On 01/02/2013 10:59 AM, Paul Berry wrote:
This patch enhances the varying packing code so that flat varyings of
uint, int, and float types can be packed together.
We accomplish this in lower_packed_varyings.cpp by making the type of
all flat varyings ivec4, and then using information-preserving
On 01/04/2013 06:41 PM, Jordan Justen wrote:
This format is allowed by the GL_EXT_texture_type_2_10_10_10_REV
extension.
Signed-off-by: Jordan Justen
---
src/mesa/main/glformats.c |9 +
1 file changed, 9 insertions(+)
diff --git a/src/mesa/main/glformats.c b/src/mesa/main/glform
On 01/04/2013 06:41 PM, Jordan Justen wrote:
GTF/gles3 test suite wants this error to have higher priority
than the type checking.
If the ReadPixels call in the test has multiple errors, the test should
be changed. There is no requirement to generate a specific error when
multiple problems e
Kenneth Graunke writes:
> How about:
>
> if (optind == argc - 1) {
> filename = argv[optind];
> } else if (optind < argc) {
> usage ();
> exit (1);
> }
Thanks, that does catch an additional usage error that was let through
previously. I'
>-Original Message-
>From: Brian Paul [mailto:bri...@vmware.com]
>Sent: Monday, January 07, 2013 8:07 PM
>To: Jorge Ramirez Ortiz, HCL Europe
>Cc: Ian Romanick; mesa-dev@lists.freedesktop.org
>Subject: Re: [Mesa-dev] glxinfo proposed change
>
>On 01/07/2013 11:48 AM, Ian Romanick wrote:
>
>-Original Message-
>From: Ian Romanick [mailto:i...@freedesktop.org]
>Sent: Monday, January 07, 2013 7:48 PM
>To: Jorge Ramirez Ortiz, HCL Europe
>Cc: Dan Nicholson; mesa-dev@lists.freedesktop.org
>Subject: Re: [Mesa-dev] glxinfo proposed change
>
>On 01/07/2013 06:35 AM, Jorge Ramirez O
Kenneth Graunke writes:
> generate_uniform_pull_constant_load_gen7() is only called on Gen7+, so
> the gen < 6 code is dead.
> ---
> src/mesa/drivers/dri/i965/brw_fs_emit.cpp | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/src/mesa/drivers/dri/i965/brw_fs_emit.cpp
> b/src/mesa/drivers
From: Jerome Glisse
Signed-off-by: Jerome Glisse
---
src/gallium/drivers/r300/r300_context.c | 2 +-
src/gallium/drivers/r600/r600_pipe.c | 2 +-
src/gallium/drivers/radeonsi/radeonsi_pipe.c | 2 +-
src/gallium/winsys/radeon/drm/radeon_drm_bo.c | 2 +-
sr
So first patch is the winsys change while second patch implement multi ring
in the r600g driver. It use a stack to keep track of the order into which
rings must be submited. If will only pop the necessary entry from the stack
depending on the current request.
I think this address all concern from
On 01/07/2013 11:48 AM, Ian Romanick wrote:
On 01/07/2013 06:35 AM, Jorge Ramirez Ortiz, HCL Europe wrote:
-Original Message-
From: Dan Nicholson [mailto:dbn.li...@gmail.com]
Sent: Monday, January 07, 2013 2:31 PM
To: Jorge Ramirez Ortiz, HCL Europe
Cc: mesa-dev@lists.freedesktop.org
Sub
On 01/07/2013 06:35 AM, Jorge Ramirez Ortiz, HCL Europe wrote:
-Original Message-
From: Dan Nicholson [mailto:dbn.li...@gmail.com]
Sent: Monday, January 07, 2013 2:31 PM
To: Jorge Ramirez Ortiz, HCL Europe
Cc: mesa-dev@lists.freedesktop.org
Subject: Re: [Mesa-dev] glxinfo proposed change
On 01/05/2013 11:40 AM, Jordan Justen wrote:
On Fri, Jan 4, 2013 at 5:43 PM, Ian Romanick wrote:
From: Ian Romanick
Use this method in _mesa_GetInternalformativ for both GL_SAMPLES and
GL_NUM_SAMPLE_COUNTS.
v2: internalFormat may not be color renderable by the driver, so zero
can be returned
Eric Anholt writes:
> I think the build fails unless this is put before 4/5. Or is it just
> that de translations are lost?
The latter. Some translations are lost, but there's no build failure.
> I don't think the executable modification of the script is required -- I
> suspect you saw the same
Carl Worth writes:
> As can be seen, many other translation strings already include a single
> apostrophe just fine without any escaping. This strangely-escaped apostrophe
> was causing a build failure ("invalid escape sequence") resulting in no "de"
> translations in the final options.h file.
I
Ian Romanick writes:
> On 12/20/2012 04:07 PM, Eric Anholt wrote:
>> We don't have native hardware support for these, so they get promoted to
>> RGBA, in which case we don't have hardware dealing with the channel
>> swizzling for us.
>>
>> Fixes piglit EXT_texture_snorm/texwrap formats bordercolo
On 01/04/2013 06:41 PM, Jordan Justen wrote:
If the source read buffer is integer based, and the the read
pixels type is RGBA/UNSIGNED_BYTE, then use the integer pixel
conversion path.
Is there any spec justification for this? This seems... wrong.
Signed-off-by: Jordan Justen
---
src/mes
On 01/04/2013 06:41 PM, Jordan Justen wrote:
Changes based on GTF/gles3 conformance test suite.
Signed-off-by: Jordan Justen
---
src/mesa/main/teximage.c | 62 +-
1 file changed, 45 insertions(+), 17 deletions(-)
diff --git a/src/mesa/main/texim
On 01/04/2013 06:41 PM, Jordan Justen wrote:
Signed-off-by: Jordan Justen
---
src/mesa/main/teximage.c | 29 +
1 file changed, 29 insertions(+)
diff --git a/src/mesa/main/teximage.c b/src/mesa/main/teximage.c
index ac60a21..169e768 100644
--- a/src/mesa/main/tex
On 01/04/2013 06:41 PM, Jordan Justen wrote:
This returns the current read renderbuffer for the specified
format type.
Signed-off-by: Jordan Justen
---
src/mesa/main/framebuffer.c | 20
src/mesa/main/framebuffer.h |4
2 files changed, 24 insertions(+)
diff -
On 01/04/2013 06:41 PM, Jordan Justen wrote:
Signed-off-by: Jordan Justen
---
src/mesa/main/teximage.c | 21 ++---
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/src/mesa/main/teximage.c b/src/mesa/main/teximage.c
index d87808d..ac60a21 100644
--- a/src/mesa/
On 01/04/2013 06:41 PM, Jordan Justen wrote:
From: Matt Turner
This function checks for ES3 compatible
format/type/internalFormat/dimension combinations.
[jordan.l.jus...@intel.com: additional tweaks for gles3-gtf]
Signed-off-by: Jordan Justen
---
src/mesa/main/glformats.c | 439 ++
On 01/04/2013 06:41 PM, Jordan Justen wrote:
Signed-off-by: Jordan Justen
---
src/mesa/main/fbobject.c | 57 +++---
1 file changed, 54 insertions(+), 3 deletions(-)
diff --git a/src/mesa/main/fbobject.c b/src/mesa/main/fbobject.c
index f1cf700..097e0
On 01/04/2013 06:41 PM, Jordan Justen wrote:
Signed-off-by: Jordan Justen
I believe this should be marked for the stable branch.
---
src/mesa/main/format_unpack.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/src/mesa/main/format_unpack.c b/src/mesa/main/format
On 01/04/2013 06:41 PM, Jordan Justen wrote:
Signed-off-by: Jordan Justen
---
src/mesa/main/fbobject.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/mesa/main/fbobject.c b/src/mesa/main/fbobject.c
index 4b7d4ab..f1cf700 100644
--- a/src/mesa/main/fbobject.c
+++ b/
On Mon, Jan 7, 2013 at 8:16 AM, Anuj Phogat wrote:
> This patch fixes a case when blitting to a framebuffer with
> renderbuffers/textures attached to GL_COLOR_ATTACHMENT{1, 2, ...}.
> Earlier we were incorrectly blitting to GL_COLOR_ATTACHMENT0 by default.
>
> Signed-off-by: Anuj Phogat
> ---
Th
On 2013-01-07 02:48, Brian Paul wrote:
On 01/06/2013 03:14 PM, Alex wrote:
* We have a symbol conflict as rtasm in
Mesa collides with rtasm in gallium.
* As us linking gallium and mesa together
is an edge case, lets just omit the rtasm
code from Mesa as we should be going
llvmpipe s
https://bugs.freedesktop.org/show_bug.cgi?id=58665
--- Comment #10 from Brian Paul ---
I tested softpipe on the PS3 (big-endian) a few years ago and remember fixing
an endian issue then (and things looked good thereafter). Perhaps something's
been broken since.
--
You are receiving this mail b
https://bugs.freedesktop.org/show_bug.cgi?id=58665
--- Comment #9 from Michel Dänzer ---
(In reply to comment #2)
> If you look at src/gallium/state_trackers/glx/xlib/xm_api.c in the
> choose_pixel_format() function you'll see code that chooses a PIPE_FORMAT_x
> format by checking the visual's re
https://bugs.freedesktop.org/show_bug.cgi?id=58665
--- Comment #8 from Brian Paul ---
Yeah, for softpipe, src/gallium/state_trackers/glx/xlib/xm_api.c is the file to
look at.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freedesktop.org/show_bug.cgi?id=58665
--- Comment #7 from Stefan de Konink ---
Created attachment 72640
--> https://bugs.freedesktop.org/attachment.cgi?id=72640&action=edit
glxinfo right colours
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=58665
--- Comment #6 from Stefan de Konink ---
Created attachment 72639
--> https://bugs.freedesktop.org/attachment.cgi?id=72639&action=edit
glxinfo wrong colours
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=58665
--- Comment #5 from Brian Paul ---
What is the output of running glxinfo when you see the wrong colors?
--
You are receiving this mail because:
You are the assignee for the bug.
___
mesa-dev mailing l
https://bugs.freedesktop.org/show_bug.cgi?id=58665
--- Comment #4 from Stefan de Konink ---
How can I verify this?
--
You are receiving this mail because:
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http:
https://bugs.freedesktop.org/show_bug.cgi?id=58665
--- Comment #3 from Michel Dänzer ---
(In reply to comment #2)
> src/gallium/state_trackers/glx/xlib/xm_api.c
Is this bug report about that, not about src/mesa/drivers/dri/swrast or
src/mesa/drivers/x11 ?
--
You are receiving this mail because
On 01/06/2013 03:14 PM, Alex wrote:
* We have a symbol conflict as rtasm in
Mesa collides with rtasm in gallium.
* As us linking gallium and mesa together
is an edge case, lets just omit the rtasm
code from Mesa as we should be going
llvmpipe soon :)
---
src/mesa/SConscript |2
On 07.01.2013 17:03, Marek Olšák wrote:
On Mon, Jan 7, 2013 at 3:45 PM, Christian König wrote:
On 07.01.2013 01:24, Marek Olšák wrote:
On Sun, Jan 6, 2013 at 11:58 PM, Jerome Glisse wrote:
On Sun, Jan 6, 2013 at 4:00 PM, Marek Olšák wrote:
I agree with Christian. You can use a separate ins
On Mon, Jan 7, 2013 at 11:03 AM, Marek Olšák wrote:
> On Mon, Jan 7, 2013 at 3:45 PM, Christian König
> wrote:
>> On 07.01.2013 01:24, Marek Olšák wrote:
>>>
>>> On Sun, Jan 6, 2013 at 11:58 PM, Jerome Glisse wrote:
On Sun, Jan 6, 2013 at 4:00 PM, Marek Olšák wrote:
>
> I agr
Changes in fbobject.c fix a case when blitting to a framebuffer with
renderbuffers/textures attached to GL_COLOR_ATTACHMENT{i} (where i!=0).
Earlier it skips color blitting if nothing is found attached to
GL_COLOR_ATTACHMENT0.
Changes in swrast/s_blit.c fix a blitting case when drawAttachment->Tex
This allows query on default framebuffer in
glGetFramebufferAttachmentParameteriv()
for gles3. Fixes unexpected GL errors in gles3 conformance test case:
framebuffer_blit_functionality_multisampled_to_singlesampled_blit
V2: Use _mesa_is_gles3() check to restrict allowed attachment types to
specif
This patch enables blitting to multiple color attachments of a framebuffer.
It also fixes a case when blitting to a framebuffer with renderbuffer/texture
attached to non-zero attachment point i.e. GL_COLOR_ATTACHMENT{1, 2, ...}.
Earlier we were incorrectly blitting to GL_COLOR_ATTACHMENT0 by defaul
This patch fixes a case when blitting to a framebuffer with
renderbuffers/textures attached to GL_COLOR_ATTACHMENT{1, 2, ...}.
Earlier we were incorrectly blitting to GL_COLOR_ATTACHMENT0 by default.
Signed-off-by: Anuj Phogat
---
src/mesa/drivers/dri/i965/brw_blorp_blit.cpp |5 +-
src/mesa/
This patch rewrites _mesa_meta_BlitFrameBuffer() function to add support
for blitting with GLSL/GLSL ES shaders. These changes were required to
support glBlitFrameBuffer() in gles3. This patch, along with other patches
in this series, make 16 failing framebuffer_blit test cases in gles3
conformance
V2:
If mask has GL_STENCIL_BUFFER_BIT set, the depth formats for readRenderBuffer
and drawRenderBuffer must match unless one of the two buffers doesn't have
depth, in which case it's not blitted, so the format check should be ignored.
Same comment goes for stencil formats in depth renderbuffers if
From: Kenneth Graunke
Nothing was explicitly checking this.
Reviewed-by: Anuj Phogat
Signed-off-by: Anuj Phogat
---
src/mesa/main/buffers.c | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/src/mesa/main/buffers.c b/src/mesa/main/buffers.c
index c241338..ad585
From: Kenneth Graunke
In ES 3.0, when calling glDrawBuffers() on the window system
framebuffer, the only valid targets are GL_NONE or GL_BACK. Since there
is no stereo rendering in ES 3.0, this is a single buffer, unlike
desktop where it may be two (and thus isn't allowed).
For single-buffered
These patches are based on gles3 branch of mesa. They were circulated
through the list in last week of Jan. After that I've made few changes
based on suggestions from Ian, ken and Brian. All patches collectively
fix 17 failing test cases in gles3 conformance framebuffer_blit
and framebuffer_srgb_de
On Mon, Jan 7, 2013 at 3:45 PM, Christian König wrote:
> On 07.01.2013 01:24, Marek Olšák wrote:
>>
>> On Sun, Jan 6, 2013 at 11:58 PM, Jerome Glisse wrote:
>>>
>>> On Sun, Jan 6, 2013 at 4:00 PM, Marek Olšák wrote:
I agree with Christian. You can use a separate instance of
radeon
On 07.01.2013 01:24, Marek Olšák wrote:
On Sun, Jan 6, 2013 at 11:58 PM, Jerome Glisse wrote:
On Sun, Jan 6, 2013 at 4:00 PM, Marek Olšák wrote:
I agree with Christian. You can use a separate instance of
radeon_winsys_cs for the DMA CS. The winsys exposes all the functions
you need (except on
>-Original Message-
>From: Dan Nicholson [mailto:dbn.li...@gmail.com]
>Sent: Monday, January 07, 2013 2:31 PM
>To: Jorge Ramirez Ortiz, HCL Europe
>Cc: mesa-dev@lists.freedesktop.org
>Subject: Re: [Mesa-dev] glxinfo proposed change
>
>On Mon, Jan 7, 2013 at 5:06 AM, Jorge Ramirez Ortiz,
On Mon, Jan 7, 2013 at 5:06 AM, Jorge Ramirez Ortiz, HCL Europe
wrote:
> Hi all,
>
> Does this patch make sense? glVersion can be NULL and not having the changes
> below could cause a SIGSEGV
>
> [jramirez@calypso-2 mesa-demos.git (tmp *)]$ git diff src/xdemos/glxinfo.c
> diff --git a/src/xdemos
Hi all,
Does this patch make sense? glVersion can be NULL and not having the changes
below could cause a SIGSEGV
[jramirez@calypso-2 mesa-demos.git (tmp *)]$ git diff src/xdemos/glxinfo.c
diff --git a/src/xdemos/glxinfo.c b/src/xdemos/glxinfo.c
index aa6430d..97b6539 100644
--- a/src/xdemos/glxi
As a convenience, --enable-debug will add "-g -O0" to the compiler flags when
GCC is in use. This is helpful but has the drawback that it will override the
user's optimization settings. Instead, only add the convenience "-g -O0" when
the user has not set their compiler flags at all.
Signed-off-by:
Since mesa occasionally alters the users's compiler and linker flags, it's
useful to keep track of their original settings so the user's intentions are
respected. However, since mesa may alter the variables with settings required
for the build, they should not be restored to their original settings
On Mon, Dec 31, 2012 at 6:03 AM, Dan Nicholson wrote:
> On Sun, Dec 23, 2012 at 3:41 AM, Johannes Obermayr
> wrote:
>> Am Samstag, 22. Dezember 2012, 16:34:48 schrieben Sie:
>>> On Sat, Dec 22, 2012 at 10:47 AM, Johannes Obermayr
>>> wrote:
>>> > Am Samstag, 22. Dezember 2012, 09:21:33 schrieb M
On Thursday, January 03, 2013 05:00:39 PM Eric Anholt wrote:
>
> Sorry for the delay, I think we all disappeared over the holidays.
>
> Let's see if I've got this all right. It looks like today we have
> extensions for:
>
> OES_EGL_image:
> * turn an EGLImage into a 0-level texture
> * turn an
On Sat, Jan 5, 2013 at 8:11 AM, Jordan Justen wrote:
> Changes based on GTF/gles3 conformance test suite.
>
> Signed-off-by: Jordan Justen
> ---
> src/mesa/main/teximage.c | 62
> +-
> 1 file changed, 45 insertions(+), 17 deletions(-)
>
> diff --git
On 12/27/2012 10:22 PM, Chad Versace wrote:
On 12/20/2012 09:00 PM, Tapani Pälli wrote:
On 12/21/2012 01:11 AM, Chad Versace wrote:
In Jelly Bean, the interface to ANativeWindow changed. The change included
adding a new parameter the queueBuffer and dequeueBuffer methods and
removing the lockBu
81 matches
Mail list logo
