On Wed, Jul 02, 2014 at 12:33:16PM -0700, Jordan Justen wrote:
> On Wed, Jul 2, 2014 at 5:39 AM, Pohjolainen, Topi
> wrote:
> > On Tue, Jul 01, 2014 at 04:53:06PM -0700, Jordan Justen wrote:
> >> We now skip allocating a hiz miptree for gen7. Instead, we calculate
> >> the required hiz buffer para
On Wed, Jul 02, 2014 at 07:00:06PM +0100, Neil Roberts wrote:
> Adds an implementation of the ClearTexSubImage driver entry point that tries
> to set up an FBO to render to the texture and then calls glClear with a
> scissor to perform the actual clear. If an FBO can't be created for the
> texture
The GLSL specification says that either carriage-return, line-feed, or both
together can be used to terminate lines. Further, it says that when used
together, the pair of terminators shall be interpreted as a single line.
This final requirement has not been respected by glcpp up until now, (it has
The GLSL specification has a very broad definition of what is a
newline. Namely, it can be the carriage-return character, '\r', the newline
character, '\n', or any combination of the two, (though in combination, the
two are treated as a single newline).
Here, we add a new test-runner, glcpp-test-c
Sometimes the newline separator is a single character, and sometimes it is two
characters. Before we can fold away and line-continuation backslashes, we
identify the flavor of line separator that is in use.
With this identified, we then correctly search for backslashes followed
immediately by the
The (optional) test-specific command-line arguments to be passed to glcpp are
embedded within the source files of some tests, and glcpp-test uses grep to
extract them.
Of course, grep is line-based and looks for the native line-separator to
determine line boundaries. So, for files using non-native
Some tests were failing because the message printed by #error was including a
'\r' character from the source file in its output.
This is easily avoided by fixing the regular expression for #error to never
include any of the possible newline characters, (neither '\r' nor '\n').
With this commit 2
This small series expands the glcpp-test test suite to be able to test all
variations of newlines as allowed by the GLSL specification. It then fixes 4
bugs exposed by that testing until the entire test suite can pass with each of
the 4 allowed newline variations.
The new testing is not yet hooked
https://bugs.freedesktop.org/show_bug.cgi?id=80836
Samuel Iglesias changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Wed, 2014-07-02 at 21:04 +0200, Andreas Boll wrote:> I'd like to make a new demos release on Friday, July 4th.> The last release was on February 24th, 2013. Additionally this> release is needed to fix the build with mesa 10.2. (fdo#78101)> > Any objections?> > Also I'd like to get these 3 patc
On Tue, Jul 1, 2014 at 5:25 PM, Kenneth Graunke wrote:
> The GL_TRANSFORM_FEEDBACK_PRIMITIVES_WRITTEN counter is not supposed to
> increment during glGenerateMipmap(). I don't think either counter is
> supposed to increment during most meta operations, so simply turn off
> statistics during those
On Tue, Jul 1, 2014 at 5:31 PM, Kenneth Graunke wrote:
> On Tuesday, July 01, 2014 03:25:49 PM Carl Worth wrote:
>> There is no behavioral change here. It's just easier to verify that lists
>> of start conditions include all expected conditions when they appear in a
>> consistent order.
>>
>> The
Folding for conversions: F32/64->(U16/32, S16/32) and (U16/32, S16/32)->F32
No piglit regressions observed!
Signed-off-by: Tobias Klausmann
---
.../drivers/nouveau/codegen/nv50_ir_peephole.cpp | 74 ++
1 file changed, 74 insertions(+)
diff --git a/src/gallium/drivers/nouve
On Wed, Jul 2, 2014 at 4:03 PM, Roland Scheidegger wrote:
> Actually on second thought, because centroid and sample are mutually
> exclusive (or more generally, the "Interpolate" member determines "how"
> interpolation is done, whereas these two determine the "where")
> something like this might b
On Wed, Jul 2, 2014 at 3:04 PM, Andreas Boll wrote:
> I'd like to make a new demos release on Friday, July 4th.
> The last release was on February 24th, 2013. Additionally this
> release is needed to fix the build with mesa 10.2. (fdo#78101)
>
> Any objections?
Not an objection, but since there's
https://bugs.freedesktop.org/show_bug.cgi?id=80183
--- Comment #1 from Roland Scheidegger ---
Sorry that trace is a bit too much to handle. I looked at it but I can't really
make out any difference wrt use of glsl shader or not at all (note that for the
gallium driver this cannot make a differenc
Thank you all for your help. Finally, it works, although I have to force
the OpenGL version with MESA_GL_VERSION_OVERRIDE and its GLSL partner,
because KHR_create_context is not supported under LLVMpipe - if those
environment variables are not set, the maximum that can be got is a 3.0
context. I su
What Mesa version are you using? IIRC OpenGL 3.3 is only supported in
llvmpipe in mesa 10.3 and newer. Using MESA_GL_VERISON_OVERRIDE just fakes
the version string, it doesn't change what functions you can actually link
to.
Also, that also means for compatibility reasons you might want to request
https://bugs.freedesktop.org/show_bug.cgi?id=80836
Priority: medium
Bug ID: 80836
Keywords: bisected, regression
CC: i...@freedesktop.org, sigles...@igalia.com
Assignee: mesa-dev@lists.freedesktop.org
Summary: [llvmpipe] [softpip
https://bugs.freedesktop.org/show_bug.cgi?id=75286
Emil Velikov changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=80835
Priority: medium
Bug ID: 80835
Keywords: regression
CC: bri...@vmware.com, srol...@vmware.com
Assignee: mesa-dev@lists.freedesktop.org
Summary: [llvmpipe] piglit fs-struct-pad re
Tom Stellard writes:
> On Thu, Jun 26, 2014 at 04:15:39PM +0200, Francisco Jerez wrote:
>> Tom Stellard writes:
>>
>> > v2:
>> > - Report correct values for CL_DEVICE_NATIVE_VECTOR_WIDTH_DOUBLE and
>> > CL_DEVICE_PREFERRED_VECTOR_WIDTH_DOUBLE.
>> > - Only define cl_khr_fp64 if the exten
On 07/02/2014 04:31 PM, Ian Romanick wrote:
On 07/02/2014 07:29 AM, Brian Paul wrote:
On 07/02/2014 06:49 AM, Brian Paul wrote:
On 07/02/2014 06:36 AM, Brian Paul wrote:
On 07/01/2014 08:43 PM, Michel Dänzer wrote:
On 02.07.2014 00:43, Brian Paul wrote:
Module: Mesa
Branch: master
Commit: f4
On 07/02/2014 07:29 AM, Brian Paul wrote:
> On 07/02/2014 06:49 AM, Brian Paul wrote:
>> On 07/02/2014 06:36 AM, Brian Paul wrote:
>>> On 07/01/2014 08:43 PM, Michel Dänzer wrote:
On 02.07.2014 00:43, Brian Paul wrote:
> Module: Mesa
> Branch: master
> Commit: f4b0ab7afd83c81132921
Reviewed-by: Jordan Justen
On Fri, Jun 27, 2014 at 2:21 AM, Chris Forbes wrote:
> If another layout qualifier appeared to the left of `invocations` in the
> GS input layout declaration, the invocation count would be dropped on
> the floor.
>
> Fixes the piglit test:
>
> spec/ARB_transform_feedba
On Jul 2, 2014, at 12:52 PM, Matt Arsenault wrote:
>
> On Jul 2, 2014, at 12:48 PM, Tom Stellard wrote:
>
>> ---
>> src/gallium/state_trackers/clover/api/device.cpp | 3 +--
>> src/gallium/state_trackers/clover/core/device.cpp | 6 ++
>> src/gallium/state_trackers/clover/core/device.hpp |
Previously, we were assuming that kernel metadata nodes only had 1 operand.
Kernels which have attributes can have more than 1, e.g.:
!0 = metadata !{void (i32 addrspace(1)*)* @testKernel, metadata !1}
!1 = metadata !{metadata !"work_group_size_hint", i32 4, i32 1, i32 1}
Attempting to get the ke
A driver which doesn't have async flip support will queue up flips without any
way to replace them afterwards. This means we've got a scanout buffer pinned
as soon as we schedule a flip and so we need another buffer to keep from
stalling.
When vblank_mode=0, if there are only three buffers we do:
Previously, we were passing these through, just like any other pragma. But the
downstream compiler was tripping up on them. It seems easier to swallow these
in the preprocessor and not pass them on at all rather than fixing the
downstream compiler.
This fixes the following Khronos GLES3 CTS tests:
Prior to this commit, the following snippet would trigger an error in glcpp:
#define FOO defined BAR
#if FOO
#endif
The problem was that support for the "defined" operator was implemented within
the grammar, (where the parser was parsing the tokens of the condition
itself)
On Wed, Jul 2, 2014 at 4:30 PM, Ilia Mirkin wrote:
> Signed-off-by: Ilia Mirkin
> Tested-by: Tobias Droste
> ---
>
> In addition to the existing ARB_fragment_layer_viewport piglits passing and
> the new AMD_vertex_shader_viewport_index piglit that is on the list passing,
> Tobias did a regressio
I think that with these two, I've completed my recent goal to bring glcpp into
conformance with the latest Khronos GLES3 conformance tests. I'll be doing
some full test runs over the CTS tests to see if I've missed anything.
The first patch here is a fairly trivial thing, (make glcpp emit a blank
Grigori Goronzy wrote:
On 02.07.2014 22:18, Andy Furniss wrote:
Before I knew how to get field sync to use my TVs deinterlacer I had to
modify mesa so that I could use the vdpau de-interlacer(s), when I did
this I noticed that 422 didn't work and looked the same as it does now
this has gone in
Signed-off-by: Ilia Mirkin
Reviewed-by: Kenneth Graunke
Tested-by: Tobias Droste
---
src/mesa/main/extensions.c | 1 +
src/mesa/main/mtypes.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/src/mesa/main/extensions.c b/src/mesa/main/extensions.c
index 6f25361..92e3f0d 100644
--- a/src
The assumption is that any driver capable of emitting layer from the
vertex shader and supporting viewports should be able to also handle
emitting viewport index from the vertex shader.
Signed-off-by: Ilia Mirkin
Tested-by: Tobias Droste
---
docs/relnotes/10.3.html| 2 +-
src/me
Signed-off-by: Ilia Mirkin
Tested-by: Tobias Droste
---
In addition to the existing ARB_fragment_layer_viewport piglits passing and
the new AMD_vertex_shader_viewport_index piglit that is on the list passing,
Tobias did a regression comparison to an earlier run and found no regressions.
src/ga
Signed-off-by: Ilia Mirkin
Reviewed-by: Kenneth Graunke
Tested-by: Tobias Droste
---
src/glsl/builtin_variables.cpp | 2 ++
src/glsl/glcpp/glcpp-parse.y| 3 +++
src/glsl/glsl_parser_extras.cpp | 1 +
src/glsl/glsl_parser_extras.h | 2 ++
4 files changed, 8 insertions(+)
diff --git a/src
Signed-off-by: Ilia Mirkin
---
docs/relnotes/10.3.html | 1 +
src/mesa/drivers/dri/i965/intel_extensions.c | 4 +++-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/docs/relnotes/10.3.html b/docs/relnotes/10.3.html
index 9af7210..6090a92 100644
--- a/docs/relnot
On 02.07.2014 22:18, Andy Furniss wrote:
>
> Before I knew how to get field sync to use my TVs deinterlacer I had to
> modify mesa so that I could use the vdpau de-interlacer(s), when I did
> this I noticed that 422 didn't work and looked the same as it does now
> this has gone in with my si.
>
A
Grigori Goronzy wrote:
On 18.06.2014 13:11, Christian König wrote:
@Grigori: Should I push it or did you got your account in the
meantime?
Bit late but I only just noticed this went in.
This is a really useful feature for me, having recently got a radeonsi,
as it lets me use my tvs deinterlac
Assuming this causes no piglit regressions,
Reviewed-by: Chris Forbes
Can we get some piglits which demonstrate these problems? oglconform
is too secret.
On Wed, Jul 2, 2014 at 10:54 PM, Popov, Pavel E wrote:
> Hi Chris,
>
> Could you review this patch?
>
> Probably a better solution here is t
Actually on second thought, because centroid and sample are mutually
exclusive (or more generally, the "Interpolate" member determines "how"
interpolation is done, whereas these two determine the "where")
something like this might be better:
struct tgsi_declaration_interp
{
unsigned Interpolate
On 07/02/2014 01:04 PM, Andreas Boll wrote:
I'd like to make a new demos release on Friday, July 4th.
The last release was on February 24th, 2013. Additionally this
release is needed to fix the build with mesa 10.2. (fdo#78101)
Any objections?
Sounds great.
Also I'd like to get these 3 patc
On Jul 2, 2014, at 12:48 PM, Tom Stellard wrote:
> ---
> src/gallium/state_trackers/clover/api/device.cpp | 3 +--
> src/gallium/state_trackers/clover/core/device.cpp | 6 ++
> src/gallium/state_trackers/clover/core/device.hpp | 1 +
> 3 files changed, 8 insertions(+), 2 deletions(-)
>
> diff
v2:
- Report correct values for CL_DEVICE_NATIVE_VECTOR_WIDTH_DOUBLE
and CL_DEVICE_PREFERRED_VECTOR_WIDTH_DOUBLE.
- Only define cl_khr_fp64 if the extension is supported.
- Remove trailing space from extension string.
- Rename device query function from cl_khr_fp86() to
has_doubles(
---
src/gallium/state_trackers/clover/api/device.cpp | 3 +--
src/gallium/state_trackers/clover/core/device.cpp | 6 ++
src/gallium/state_trackers/clover/core/device.hpp | 1 +
3 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/src/gallium/state_trackers/clover/api/device.cpp
b/s
Reviewed-by: Jordan Justen
On Wed, Jul 2, 2014 at 12:38 AM, Samuel Iglesias Gonsalvez
wrote:
> This patch fixes the duplicated layout qualifier detection
> for geometry shader's layout qualifiers.
>
> Also it makes the detection code more legible by defining
> allowed_duplicates_mask variable.
>
On Wed, Jul 2, 2014 at 5:39 AM, Pohjolainen, Topi
wrote:
> On Tue, Jul 01, 2014 at 04:53:06PM -0700, Jordan Justen wrote:
>> We now skip allocating a hiz miptree for gen7. Instead, we calculate
>> the required hiz buffer parameters and allocate a bo directly.
>>
>> Signed-off-by: Jordan Justen
>>
On Thu, Jun 26, 2014 at 04:15:39PM +0200, Francisco Jerez wrote:
> Tom Stellard writes:
>
> > v2:
> > - Report correct values for CL_DEVICE_NATIVE_VECTOR_WIDTH_DOUBLE and
> > CL_DEVICE_PREFERRED_VECTOR_WIDTH_DOUBLE.
> > - Only define cl_khr_fp64 if the extension is supported.
> > - Remo
On Wed, Jul 02, 2014 at 06:29:25PM +0200, Laurent Carlier wrote:
> Le mercredi 25 juin 2014, 11:58:47 Michel Dänzer a écrit :
> > On 25.06.2014 09:15, Tom Stellard wrote:
> > > https://bugs.freedesktop.org/show_bug.cgi?id=80015
> > >
> > > CC: "10.1 10.2"
> > > ---
> > >
> > > src/gallium/drive
From: Fredrik Höglund
Updated patch for refactored glxinfo/wglinfo code by Andreas Boll.
Signed-off-by: Andreas Boll
---
src/xdemos/glinfo_common.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/xdemos/glinfo_common.c b/src/xdemos/glinfo_common.c
index d5d466a..1326a86 100644
--- a
From: Fredrik Höglund
Updated patch for refactored glxinfo/wglinfo code by Brian Paul.
Signed-off-by: Brian Paul
Signed-off-by: Andreas Boll
---
src/xdemos/glinfo_common.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/src/xdemos/glinfo_common.c b/src/xdemos/glinf
From: Fredrik Höglund
Updated patch for refactored glxinfo/wglinfo code by Andreas Boll.
Signed-off-by: Andreas Boll
---
src/xdemos/glinfo_common.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/src/xdemos/glinfo_common.c b/src/xdemos/glinfo_common.c
index 0037ac7..d5d466a 100644
---
I'd like to make a new demos release on Friday, July 4th.
The last release was on February 24th, 2013. Additionally this
release is needed to fix the build with mesa 10.2. (fdo#78101)
Any objections?
Also I'd like to get these 3 patches included in the new release.
Andreas.
Fredrik Höglund (3)
On Wed, Jul 2, 2014 at 2:00 PM, Neil Roberts wrote:
> From: Ilia Mirkin
>
> Signed-off-by: Ilia Mirkin
> Reviewed-by: Neil Roberts
> ---
> src/mapi/glapi/gen/ARB_clear_texture.xml | 34
>
> src/mapi/glapi/gen/gl_API.xml| 6 +-
> src/mesa/main/
From: Ilia Mirkin
Signed-off-by: Ilia Mirkin
Reviewed-by: Neil Roberts
---
src/mapi/glapi/gen/ARB_clear_texture.xml | 34
src/mapi/glapi/gen/gl_API.xml| 6 +-
src/mesa/main/extensions.c | 1 +
src/mesa/main/mtypes.h
Adds an implmentation of the ClearTexSubImage driver entry point that just
maps the texture and writes the values in. The extension is not yet enabled by
default because it doesn't work with multisample textures as they don't have a
simple linear layout.
Reviewed-by: Jason Ekstrand
---
src/mesa/
Adds an implementation of the ClearTexSubImage driver entry point that tries
to set up an FBO to render to the texture and then calls glClear with a
scissor to perform the actual clear. If an FBO can't be created for the
texture then it will fall back to using _mesa_store_ClearTexSubImage.
When us
This adds the driver entry point for glClearTexSubImage and fills in the
_mesa_ClearTexImage and _mesa_ClearTexSubImage functions that call it.
v2: Don't clear some of the images if only one of them makes an error
Reviewed-by: Jason Ekstrand
---
src/mesa/main/dd.h | 14 +++
src/mesa/main
In texture_error_check() there was a snippet of code to check whether the
given format and internal format are basically compatible. This has been split
out into its own static helper function so that it can be used by an
implementation of glClearTexImage too.
---
src/mesa/main/teximage.c | 59 +++
Here is version 3 of the patches to implement GL_ARB_clear_texture. The main
changes are:
• The extension is now only enabled for the i965 driver. I've removed the
patch to add a place to enable extensions for all DRI drivers.
• It now checks for potential errors that would occur when clearing
When attaching a texture to a framebuffer it was previously using the size of
the texture minus the border when determining the renderbuffer size. However
the size of the image buffer includes the border so when used with the swrast
driver it would end up calculating the wrong stride and it would r
2014-07-02 18:48 GMT+02:00 Emil Velikov :
> On 02/07/14 13:11, Andreas Pokorny wrote:
> > Hi,
> > Still trying the patch. Meanwhile I found two more things here:
> >
> > [...]
> >
> > The driver_name is later freed with free, so to avoid abort strdup should
> > be necessary.
> >
> The free snuck i
I don't have much of an idea how the interaction with per sample shading
should look like, but this looks alright to me.
Roland
Am 02.07.2014 03:55, schrieb Ilia Mirkin:
> Signed-off-by: Ilia Mirkin
> ---
>
> Not sure if this is the right approach or if I should combine it with Centroid
> more
https://bugs.freedesktop.org/show_bug.cgi?id=80821
Kalrish Bäakjen changed:
What|Removed |Added
CC||kalrish.ant...@gmail.com
--
You are r
Am 02.07.2014 16:57, schrieb Ilia Mirkin:
> If multiple viewports are supported, that implies the presence of a GS
> and layered rendering, so we can enable ARB_fragment_layer_viewport as
> well.
>
> Signed-off-by: Ilia Mirkin
> ---
>
> OK... this has been fun. The r600g change has been reviewed
https://bugs.freedesktop.org/show_bug.cgi?id=80821
Priority: medium
Bug ID: 80821
Assignee: mesa-dev@lists.freedesktop.org
Summary: When LIBGL_ALWAYS_SOFTWARE is set, the
KHR_create_extension is not supported
Severity: enhanc
On 02/07/14 13:11, Andreas Pokorny wrote:
> Hi,
> Still trying the patch. Meanwhile I found two more things here:
>
>
> 2014-06-15 13:49 GMT+02:00 Giovanni Campagna :
>
>> From: Giovanni Campagna
>> [..]
>> static int
>> +dri_screen_create_swrast(struct gbm_dri_device *dri)
>> +{
>> + int re
Le mercredi 25 juin 2014, 11:58:47 Michel Dänzer a écrit :
> On 25.06.2014 09:15, Tom Stellard wrote:
> > https://bugs.freedesktop.org/show_bug.cgi?id=80015
> >
> > CC: "10.1 10.2"
> > ---
> >
> > src/gallium/drivers/radeon/radeon_setup_tgsi_llvm.c | 2 +-
> > 1 file changed, 1 insertion(+), 1
On Wed, Jul 2, 2014 at 10:57 AM, Ilia Mirkin wrote:
> If multiple viewports are supported, that implies the presence of a GS
> and layered rendering, so we can enable ARB_fragment_layer_viewport as
> well.
>
> Signed-off-by: Ilia Mirkin
> ---
>
> OK... this has been fun. The r600g change has been
Ian Romanick writes:
> Every driver in Mesa supports GL_EXT_framebuffer_object and
> GL_EXT_framebuffer_blit. […]
>
> So, I don't think this check adds any value.
Ok.
>> + /* This probably won't work with images that have a border */
>> + if (texImage->Border != 0)
>> + return false;
>
On Sat, Jun 28, 2014 at 01:12:49PM +0200, Marek Olšák wrote:
> The one that increases the number of input SGPRs to 22 (16 user + 6
> streamout) in the calling convention. I don't remember the name.
> Please "git blame" on the calling convention.
>
I merged this patch into LLVM 3.4.2, which was re
On Wed, 2014-07-02 at 15:40 +0100, Steven Newbury wrote:
> On Wed, 2014-07-02 at 10:59 +0200, Iago Toral wrote:
> > Oh, I just noticed there was some problem with the first reply I
> > sent
> > and Chris and Steven got out of the CC in my reply, so adding them
> > back
> > now.
> > Steven: th
Thanks Tobias! I've pushed this change now.
On Wed, Jul 2, 2014 at 12:49 AM, Tobias Droste wrote:
> Hi,
>
> I did a piglit run with the gpu.py profile with and without the patch.
> There were some switches from pass->fail and fail->pass in
> spec/glsl-1.50/execution/geometry/end-primitive but the
If multiple viewports are supported, that implies the presence of a GS
and layered rendering, so we can enable ARB_fragment_layer_viewport as
well.
Signed-off-by: Ilia Mirkin
---
OK... this has been fun. The r600g change has been reviewed and tested, and
now pushed. So all ARB_viewport_array-sup
On Wed, Jul 2, 2014 at 9:42 AM, Thomas Hellstrom wrote:
> On 07/02/2014 12:50 PM, Maarten Lankhorst wrote:
>> op 02-07-14 12:34, Thomas Hellstrom schreef:
>>> Hi, Rob
>>>
>>> It turns out that your patch st/xa: use pipe-loader to get screen,
>>> makes the xa tracker close the X server driver's dr
On Wed, 2014-07-02 at 10:59 +0200, Iago Toral wrote:
> Oh, I just noticed there was some problem with the first reply I sent
> and Chris and Steven got out of the CC in my reply, so adding them
> back
> now.
>
> Steven: the summary is that on IvyBridge Kenneth's second patch
> produces
> a GPU
On 07/02/2014 06:49 AM, Brian Paul wrote:
On 07/02/2014 06:36 AM, Brian Paul wrote:
On 07/01/2014 08:43 PM, Michel Dänzer wrote:
On 02.07.2014 00:43, Brian Paul wrote:
Module: Mesa
Branch: master
Commit: f4b0ab7afd83c811329211eae8167c9bf238870c
URL:
https://urldefense.proofpoint.com/v1/url?u=h
Patches 10 and 11 are:
Acked-by: Topi Pohjolainen
and the rest are (with suggestions from Chris):
Reviewed-by: Topi Pohjolainen
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
On Mon, Jun 30, 2014 at 02:40:42PM -0700, Matt Turner wrote:
> With a hack to place an exec_node in the struct in C to be at the same
> location as the inherited exec_node in C++.
Are you planning to eventually have one but not the other? If this is just
temporary it does not make a lot difference
On Mon, Jun 30, 2014 at 02:40:38PM -0700, Matt Turner wrote:
> ---
> src/mesa/drivers/dri/i965/brw_blorp_blit_eu.cpp| 2 +-
> src/mesa/drivers/dri/i965/brw_blorp_blit_eu.h | 7 +++---
> src/mesa/drivers/dri/i965/brw_defines.h| 26
> --
> src/mesa/drivers
On 07/02/2014 12:50 PM, Maarten Lankhorst wrote:
> op 02-07-14 12:34, Thomas Hellstrom schreef:
>> Hi, Rob
>>
>> It turns out that your patch st/xa: use pipe-loader to get screen,
>> makes the xa tracker close the X server driver's drm file descriptor when
>> XA initialization fails or when XA is
On 07/02/2014 06:36 AM, Brian Paul wrote:
On 07/01/2014 08:43 PM, Michel Dänzer wrote:
On 02.07.2014 00:43, Brian Paul wrote:
Module: Mesa
Branch: master
Commit: f4b0ab7afd83c811329211eae8167c9bf238870c
URL:
https://urldefense.proofpoint.com/v1/url?u=http://cgit.freedesktop.org/mesa/mesa/commit
On Tue, Jul 01, 2014 at 04:53:05PM -0700, Jordan Justen wrote:
> We are still allocating a miptree for hiz, but we only use fields from
> intel_miptree_aux_buffer. This will allow us to switch over to not
> allocating a miptree.
>
> Signed-off-by: Jordan Justen
> ---
> src/mesa/drivers/dri/i965/
On Tue, Jul 01, 2014 at 04:53:06PM -0700, Jordan Justen wrote:
> We now skip allocating a hiz miptree for gen7. Instead, we calculate
> the required hiz buffer parameters and allocate a bo directly.
>
> Signed-off-by: Jordan Justen
> ---
> src/mesa/drivers/dri/i965/intel_mipmap_tree.c | 67
> ++
On 07/01/2014 08:43 PM, Michel Dänzer wrote:
On 02.07.2014 00:43, Brian Paul wrote:
Module: Mesa
Branch: master
Commit: f4b0ab7afd83c811329211eae8167c9bf238870c
URL:
https://urldefense.proofpoint.com/v1/url?u=http://cgit.freedesktop.org/mesa/mesa/commit/?id%3Df4b0ab7afd83c811329211eae8167c9b
On Tue, 2014-07-01 at 14:45 -0700, Kenneth Graunke wrote:
> From: Cody Northrop
>
> Vectors are falling in to the ir_dereference_array() path.
>
> Without this change, the following glsl aborts the debug driver,
> or gets the wrong answer in release:
>
> mat2x2 a = mat2( vec2( 1.0, vertex.x ),
Hi,
Still trying the patch. Meanwhile I found two more things here:
2014-06-15 13:49 GMT+02:00 Giovanni Campagna :
> From: Giovanni Campagna
> [..]
> static int
> +dri_screen_create_swrast(struct gbm_dri_device *dri)
> +{
> + int ret = 0;
> +
> + dri->base.driver_name = "swrast";
> +
> +
On Sat, Jun 14, 2014 at 01:59:31AM +0100, Neil Roberts wrote:
> Adds an implementation of the ClearTexSubImage driver entry point that tries
> to set up an FBO to render to the texture and then calls glClear with a
> scissor to perform the actual clear. If an FBO can't be created for the
> texture
Hi Chris,
Could you review this patch?
Probably a better solution here is to use only one type of conversion formulas
to avoid issues like this. We can remove old formulas ("BYTE_TO_FLOAT",
"FLOAT_TO_BYTE", etc.) and use only formulas which were recently added in spec
("BYTE_TO_FLOAT_TEX", "F
op 02-07-14 12:34, Thomas Hellstrom schreef:
> Hi, Rob
>
> It turns out that your patch st/xa: use pipe-loader to get screen,
> makes the xa tracker close the X server driver's drm file descriptor when
> XA initialization fails or when XA is closed.
>
> This breaks X for example on Ubuntu 14.10 if
Hi, Rob
It turns out that your patch st/xa: use pipe-loader to get screen,
makes the xa tracker close the X server driver's drm file descriptor when
XA initialization fails or when XA is closed.
This breaks X for example on Ubuntu 14.10 if 3D is disabled (typically
on ESX). Pretty nasty bug for
Hi,
Nice patches! I found one minor issue below.
I currently try to integrate and use that locally within kvm, currently on
top of 10.2.
2014-06-15 13:49 GMT+02:00 Giovanni Campagna :
> From: Giovanni Campagna
>
> Add a new winsys and target that can be used with a dri2 state tracker and
> [..]
Ilia Mirkin writes:
> Not entirely sure how to interpret what the spec says, but something
> to potentially consider is MESA_ycbcr_texture (supported by swrast).
> RGBA 0 (black) != 0 in ycbcr... all 0's there are a green color.
The spec for the extension says:
“If is NULL, then the pointer is
Oh, I just noticed there was some problem with the first reply I sent
and Chris and Steven got out of the CC in my reply, so adding them back
now.
Steven: the summary is that on IvyBridge Kenneth's second patch produces
a GPU hang in some cases so if you are going to test it try this version
bette
On Wed, 2014-07-02 at 08:49 +0200, Iago Toral wrote:
> Hello Kenneth, Steven:
>
> On Tue, 2014-07-01 at 17:25 -0700, Kenneth Graunke wrote:
> > Previously, we only emitted 3DSTATE_SO_BUFFER and 3DSTATE_SO_DECL_LIST
> > when transform feedback was active. When it was inactive, we disabled
> > the
This patch fixes the duplicated layout qualifier detection
for geometry shader's layout qualifiers.
Also it makes the detection code more legible by defining
allowed_duplicates_mask variable.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=80778
Signed-off-by: Samuel Iglesias Gonsalvez
-
97 matches
Mail list logo
