The reality is that this doesn't matter, because we manually emit the
ARL to the sampler reladdr, and those arguments don't get an extra load
later, so it's effectively just a boolean. However having the types be
wrong is confusing and could trigger very odd bugs should usage change
down the line.
https://bugs.freedesktop.org/show_bug.cgi?id=96408
Ilia Mirkin changed:
What|Removed |Added
CC|imir...@alum.mit.edu|
--
You are
This fixes a lot of flickering in The Talos Principle on Fermi+
(tested on both GF119 and GK106). My guess is that some indices
and/or some vertex attributes are incorrectly set when emitting
data directly into the command stream rather than uploading a
user VBO.
The NV50 driver also doesn't use
For the series:
Reviewed-by: Nicolai Hähnle
On 08.06.2016 17:36, Marek Olšák wrote:
From: Marek Olšák
2% isn't much. If you think the number should be decreased, please speak up.
---
src/gallium/drivers/radeonsi/si_pipe.c | 22
From: Marek Olšák
2% isn't much. If you think the number should be decreased, please speak up.
---
src/gallium/drivers/radeonsi/si_pipe.c | 22 ++
1 file changed, 18 insertions(+), 4 deletions(-)
diff --git a/src/gallium/drivers/radeonsi/si_pipe.c
From: Marek Olšák
Latest LLVM git is required.
---
src/gallium/drivers/radeonsi/si_shader.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/src/gallium/drivers/radeonsi/si_shader.c
b/src/gallium/drivers/radeonsi/si_shader.c
index
From: Marek Olšák
---
src/gallium/drivers/radeonsi/si_shader.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/src/gallium/drivers/radeonsi/si_shader.c
b/src/gallium/drivers/radeonsi/si_shader.c
index 512db42..e563aec 100644
---
Reviewed-by: Bruce Cherniak
> On Jun 8, 2016, at 9:59 AM, Tim Rowley wrote:
>
> v2: only load the clip vertex once
>
> v3: fix clip enable logic, add cullDistance
>
> v4: remove duplicate fields in vs jit key, fix test of clip fixup
On 06/07/2016 05:00 PM, Nicolai Hähnle wrote:
From: Nicolai Hähnle
The width0/height0/depth0 on stObj may not have been set at this point.
Observed in a trace that set up levels 2..9 of a 2d texture, and set the base
level to 2, with height 1. This made the guess logic
Ilia, this patch causes a regression in the piglit
arb_uniform_buffer_object-rendering-dsa test with llvmpipe (at least).
I haven't debugged it at all.
-Brian
On 06/07/2016 08:29 PM, Ilia Mirkin wrote:
Module: Mesa
Branch: master
Commit: 6e6fd911da8a1d9cd62fe0a8a4cc0fb7bdccfe02
URL:
On 06/08/2016 09:34 AM, Ilia Mirkin wrote:
The reality is that this doesn't matter, because we manually emit the
ARL to the sampler reladdr, and those arguments don't get an extra load
later, so it's effectively just a boolean. However having the types be
wrong is confusing and could trigger
On Wed, Jun 08, 2016 at 03:44:39PM +0100, Emil Velikov wrote:
> From: Emil Velikov
>
> With earlier commit we've handled the `make distclean' out of tree
> build, yet we failed to attribute that for in-tree builds the test
> condition will return 1. Thus effectively
Emil Velikov wrote:
From: Emil Velikov
With earlier commit we've handled the `make distclean' out of tree
build, yet we failed to attribute that for in-tree builds the test
condition will return 1. Thus effectively the target will be considered
as "failed".
Fixes:
For the piglit test:
Reviewed-by: Nicolai Hähnle
On 06.06.2016 18:52, Brian Paul wrote:
On 06/06/2016 10:05 AM, Ilia Mirkin wrote:
On Mon, Jun 6, 2016 at 11:37 AM, Brian Paul wrote:
On 06/05/2016 12:24 AM, Ilia Mirkin wrote:
In the case where
v2: only load the clip vertex once
v3: fix clip enable logic, add cullDistance
v4: remove duplicate fields in vs jit key, fix test of clip fixup needed
v5: fix clipdistance linkage for slot!=0,4
v6: support clip+cull; passes most piglit clip (failures understood)
---
docs/GL3.txt
On Wed, Jun 8, 2016 at 2:34 PM, ⚛ <0xe2.0x9a.0...@gmail.com> wrote:
> Hello
>
> Mesa 12.1.0-devel (git-8c3ecde) has rendering issues when running
> "glxgears -samples N" with N >= 1 on R9 390. It was running ok
> yesterday/previously.
I reverted the problematic commit.
Marek
On 06/08/2016 01:45 AM, Ian Romanick wrote:
On 06/07/2016 04:28 PM, Nanley Chery wrote:
On Wed, May 25, 2016 at 12:52:38PM -0700, Matt Turner wrote:
On Wed, May 25, 2016 at 12:17 PM, Samuel Pitoiset
wrote:
This fixes use of compute shaders with some NVIDIA GL 4.3
Spotted when glancing at the VBO push code.
Signed-off-by: Samuel Pitoiset
---
src/gallium/drivers/nouveau/nv50/nv50_vbo.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/gallium/drivers/nouveau/nv50/nv50_vbo.c
b/src/gallium/drivers/nouveau/nv50/nv50_vbo.c
On 02/06/16 23:09, Kenneth Graunke wrote:
> i965 has no special hardware for this, so we need to pass this value in
> as a uniform (unless the TES is linked against a TCS, in which case the
> linker can just replace this with a constant).
>
> Signed-off-by: Kenneth Graunke
On 02/06/16 23:09, Kenneth Graunke wrote:
> i965 has no special hardware for this, so the best way to implement
> this is to pass it in via a uniform.
Is this comment accurate? On the next patch you implement the i965 bits,
and you only do the lowering on gen8+, mentioning that you would like to
On 02/06/16 23:09, Kenneth Graunke wrote:
> Fixes GL44-CTS.tessellation_shader.single.max_patch_vertices,
> which uses gl_PatchVerticesIn in the TES, but doesn't link against
> a TCS (which would allow the linker to lower it to a constant).
Not sure if using different CTS releases but in my case
On Tue, Jun 07, 2016 at 04:45:39PM -0700, Ian Romanick wrote:
> On 06/07/2016 04:28 PM, Nanley Chery wrote:
> > On Wed, May 25, 2016 at 12:52:38PM -0700, Matt Turner wrote:
> >> On Wed, May 25, 2016 at 12:17 PM, Samuel Pitoiset
> >> wrote:
> >>> This fixes use of
On 08/06/16 19:45, Alejandro Piñeiro wrote:
> On 02/06/16 23:09, Kenneth Graunke wrote:
>> Fixes GL44-CTS.tessellation_shader.single.max_patch_vertices,
>> which uses gl_PatchVerticesIn in the TES, but doesn't link against
>> a TCS (which would allow the linker to lower it to a constant).
> Not
On Mon, Dec 28, 2015 at 10:46 AM, Anuj Phogat wrote:
> Signed-off-by: Anuj Phogat
> ---
> src/mesa/main/texgetimage.c | 83
> +
> 1 file changed, 38 insertions(+), 45 deletions(-)
>
> diff --git
An update in graphics specs has deleted the halign and valign fields
from XY_FAST_COPY_BLT command. See mesa commit 97f0f91.
Cc: Ben Widawsky
Signed-off-by: Anuj Phogat
---
src/mesa/drivers/dri/i965/brw_tex_layout.c | 6 ++
1 file changed, 2
Hm, that's odd. I guess the buffer usage doesn't get set properly? I
won't be able to look at this until tonight at the earliest, feel free
to revert the change in the meanwhile.
-ilia
On Wed, Jun 8, 2016 at 1:25 PM, Brian Paul wrote:
> Ilia, this patch causes a regression
Glancing at the code (I don't even have a piglit checkout here):
static void
set_ubo_binding(struct gl_context *ctx, ...)
...
/* If this is a real buffer object, mark it has having been used
* at some point as a UBO.
*/
if (size >= 0)
bufObj->UsageHistory |=
From: Dave Airlie
This just moves to the new interfaces in advance of int64.
Signed-off-by: Dave Airlie
---
src/mesa/main/uniform_query.cpp | 8
src/mesa/program/ir_to_mesa.cpp | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff
From: Dave Airlie
This adds an inline and type query for if a type is 64-bit.
Fow now this is equivalent to double, but int64 will change
this.
Signed-off-by: Dave Airlie
---
src/compiler/glsl_types.h | 13 +
1 file changed, 13
From: Dave Airlie
This is just some better type safety that I noticed while working
on 64-bit integer support.
Signed-off-by: Dave Airlie
---
src/mesa/state_tracker/st_glsl_to_tgsi.cpp | 24
1 file changed, 12 insertions(+), 12
From: Dave Airlie
This uses the new types interfaces to check for 64-bit types,
as futureproofing against int64 support.
Signed-off-by: Dave Airlie
---
src/mesa/state_tracker/st_glsl_to_tgsi.cpp | 30 ++
1 file changed, 14
While writing ARB_gpu_shader_int64 I realised I needed to change
a lot of existing checks for doubles to 64bit, so I decided to
do that as much in advance as possible.
This adds a macro + interface to check if a type is 64-bit,
which currently is only true for doubles, it then uses the new
API in
From: Dave Airlie
This just moves code to the new check in advance of int64 support.
Signed-off-by: Dave Airlie
---
src/compiler/glsl_types.cpp | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/src/compiler/glsl_types.cpp
From: Dave Airlie
This is just prep work for int64 support, changing
places where 64-bit matters no doubles.
Signed-off-by: Dave Airlie
---
src/compiler/glsl/ast_to_hir.cpp| 4 ++--
src/compiler/glsl/link_uniform_initializers.cpp | 2
From: Dave Airlie
In the future int64 support will have the same requirements.
Signed-off-by: Dave Airlie
---
src/compiler/glsl/ir_set_program_inouts.cpp| 4 ++--
src/compiler/glsl/linker.cpp | 4 ++--
src/compiler/glsl_types.h
Sorry, didn't CC mesa-dev, trying again...
On Wed, Jun 8, 2016 at 4:11 PM, Kenneth Graunke wrote:
> Two dEQP tests expect INVALID_VALUE errors for negative width/height
> parameters, but get INVALID_OPERATION because they haven't actually
> created a destination image.
Two dEQP tests expect INVALID_VALUE errors for negative width/height
parameters, but get INVALID_OPERATION because they haven't actually
created a destination image. This is arguably not a bug in Mesa, as
there's no specified ordering of error conditions.
However, it's also really easy to make
Series is
Reviewed-by: Ilia Mirkin
On Wed, Jun 8, 2016 at 5:15 PM, Dave Airlie wrote:
> From: Dave Airlie
>
> This uses the new types interfaces to check for 64-bit types,
> as futureproofing against int64 support.
>
>
On Wed, Jun 8, 2016 at 5:51 PM, Dave Airlie wrote:
> From: Dave Airlie
>
> In the future int64 support will have the same requirements.
>
> Signed-off-by: Dave Airlie
> ---
> src/compiler/glsl/ir_set_program_inouts.cpp| 4 ++--
>
On Wednesday 08 June 2016, Ilia Mirkin wrote:
> Glancing at the code (I don't even have a piglit checkout here):
>
> static void
> set_ubo_binding(struct gl_context *ctx, ...)
> ...
>/* If this is a real buffer object, mark it has having been used
> * at some point as a UBO.
> */
>
[snip]
Quoting Jason Ekstrand (2016-06-08 16:20:33)
> gen_format_layout.c.mako
>
> I made this comment in the office today but I think the mako here is simple
> enough that we might be better off just putting it all in one file.
>
I know you're not a fan of separate templates, and if the
From: Dave Airlie
This enables 64-bit integer support in gallivm and
llvmpipe.
Signed-off-by: Dave Airlie
---
src/gallium/auxiliary/gallivm/lp_bld_limits.h | 1 +
src/gallium/auxiliary/gallivm/lp_bld_tgsi.c| 8 +-
From: Dave Airlie
This adds support to TGSI for 64-bit integer immediates.
Signed-off-by: Dave Airlie
---
src/gallium/auxiliary/tgsi/tgsi_dump.c | 14 ++
src/gallium/auxiliary/tgsi/tgsi_exec.c | 244 -
From: Dave Airlie
This just adds the basic support for 64-bit opcodes,
and the new types.
Signed-off-by: Dave Airlie
---
src/gallium/auxiliary/tgsi/tgsi_info.c | 54 ++
src/gallium/auxiliary/tgsi/tgsi_info.h | 4 ++-
On Wed, Jun 8, 2016 at 3:34 PM, Brian Paul wrote:
> On 06/08/2016 12:15 PM, Anuj Phogat wrote:
>>
>> On Mon, Dec 28, 2015 at 10:46 AM, Anuj Phogat
>> wrote:
>>>
>>> Signed-off-by: Anuj Phogat
>>> ---
>>>
On Thursday 09 June 2016 00:47:27 Serge Martin wrote:
> This fix getting the size of a struct arg. vec3 types still work ok.
> Only buit-in args need to have power of two alignment, getTypeAllocSize
> reports the correct size.
M. I forgot to put V2 and to fix the commit message
Reviewed-by: Marek Olšák
Marek
On Mon, Jun 6, 2016 at 10:49 PM, Bas Nieuwenhuizen
wrote:
> This fixes a problem with the CE preamble and restoring only stuff in the
> preamble when needed.
>
> To illustrate suppose we have two graphics IB's 1 and
From: Dave Airlie
This adds support for 64-bit integer constants to the parser,
ast and ir.
Signed-off-by: Dave Airlie
---
src/compiler/glsl/ast.h | 4
src/compiler/glsl/ast_to_hir.cpp | 14 ++
src/compiler/glsl/glsl_lexer.ll
From: Dave Airlie
We need builder support to implement some of the builtins.
Signed-off-by: Dave Airlie
---
src/compiler/glsl/ir_builder.cpp | 24
src/compiler/glsl/ir_builder.h | 6 ++
2 files changed, 30 insertions(+)
From: Dave Airlie
This adds 64-bit ints to the link_varyings 64-bit support.
Signed-off-by: Dave Airlie
---
src/compiler/glsl/link_varyings.h | 8
1 file changed, 8 insertions(+)
diff --git a/src/compiler/glsl/link_varyings.h
From: Dave Airlie
This adds all the opcodes to tgsi_exec for softpipe to use.
It also enables the cap.
Signed-off-by: Dave Airlie
---
src/gallium/auxiliary/tgsi/tgsi_exec.c | 104 +
src/gallium/auxiliary/tgsi/tgsi_exec.h
From: Dave Airlie
Just add support in two more places in ast parsing.
Signed-off-by: Dave Airlie
---
src/compiler/glsl/ast_to_hir.cpp | 5 +
1 file changed, 5 insertions(+)
diff --git a/src/compiler/glsl/ast_to_hir.cpp
From: Dave Airlie
TODO: go back and fill this out to avoid warnings.
Signed-off-by: Dave Airlie
---
src/gallium/include/pipe/p_defines.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/gallium/include/pipe/p_defines.h
From: Dave Airlie
This adds 64-bit integer support to some AST and IR operations
where it is needed.
Signed-off-by: Dave Airlie
---
src/compiler/glsl/ast_to_hir.cpp | 12 ++--
src/compiler/glsl/ir_validate.cpp | 4 ++--
2 files changed, 8
From: Dave Airlie
Just add support to the double case, same code should work.
Signed-off-by: Dave Airlie
---
src/compiler/glsl/link_uniform_initializers.cpp | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On 06/08/2016 12:15 PM, Anuj Phogat wrote:
On Mon, Dec 28, 2015 at 10:46 AM, Anuj Phogat wrote:
Signed-off-by: Anuj Phogat
---
src/mesa/main/texgetimage.c | 83 +
1 file changed, 38 insertions(+), 45
This fix getting the size of a struct arg. vec3 types still work ok.
Only buit-in args need to have power of two alignment, getTypeAllocSize
reports the correct size.
---
src/gallium/state_trackers/clover/llvm/invocation.cpp | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
On Jun 7, 2016 5:32 PM, "Dylan Baker" wrote:
>
> This replaces the current bash generator with a python based generator
> using mako. It's quite fast and works with both python 2.7 and python
> 3.5, and should work with 3.3+ and maybe even 3.2.
>
> It produces an almost
From: Dave Airlie
This is incomplete in the conversions area.
Signed-off-by: Dave Airlie
---
src/mesa/state_tracker/st_glsl_to_tgsi.cpp | 105 -
1 file changed, 87 insertions(+), 18 deletions(-)
diff --git
From: Dave Airlie
These are all the allowed 64-bit functions from ARB_gpu_shader_int64
spec.
Signed-off-by: Dave Airlie
---
src/compiler/glsl/builtin_functions.cpp | 173 +++-
1 file changed, 170 insertions(+), 3 deletions(-)
From: Dave Airlie
This hooks up the API to the internals for 64-bit integer uniforms.
Signed-off-by: Dave Airlie
---
src/mesa/main/uniform_query.cpp | 60 +-
src/mesa/main/uniforms.c| 170 +++-
2
From: Dave Airlie
This just adds the new operations and add 64-bit integer
support to all the existing cases where it is needed.
Signed-off-by: Dave Airlie
---
src/compiler/glsl/ir_constant_expression.cpp | 324 +++
1 file
From: Dave Airlie
Signed-off-by: Dave Airlie
---
src/mesa/state_tracker/st_extensions.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/src/mesa/state_tracker/st_extensions.c
b/src/mesa/state_tracker/st_extensions.c
index 13b0acc..b94a8cb
From: Dave Airlie
This just adds the usual boilerplate in mesa core.
Signed-off-by: Dave Airlie
---
src/mesa/main/extensions_table.h | 1 +
src/mesa/main/mtypes.h | 1 +
2 files changed, 2 insertions(+)
diff --git
From: Dave Airlie
This adds the builtins and the lexer support.
To avoid too many warnings, it adds basic
support to the type in a few other places
in mesa, mostly in the trivial places.
It also adds a query to be used later for
if a type is an integer 32 or 64.
From: Dave Airlie
As for the double code, but using the 64-bit integer conversions.
Signed-off-by: Dave Airlie
---
src/compiler/glsl/lower_packed_varyings.cpp | 62 +
1 file changed, 62 insertions(+)
diff --git
From: Dave Airlie
This adds support to call the new operations on conversions.
Signed-off-by: Dave Airlie
---
src/compiler/glsl/ast_function.cpp | 75 ++
src/compiler/glsl/ast_to_hir.cpp | 20 ++
2 files
From: Dave Airlie
This adds all the conversions in the world, I'm not 100%
sure of all of these are needed, but add all of them and
we can cut them down later.
Signed-off-by: Dave Airlie
---
src/compiler/glsl/ir.cpp | 82
From: Dave Airlie
Just add the boilerplate xml code.
Signed-off-by: Dave Airlie
---
src/mapi/glapi/gen/ARB_gpu_shader_int64.xml | 262
src/mapi/glapi/gen/Makefile.am | 1 +
src/mapi/glapi/gen/gl_API.xml
I started this quite a while back, and decided to spend some
time on it again, since it's the basis for a bunch of the newer
GL extensions.
So this is my first pass at it, it's fairly complete, but it
definitely is missing some pieces before it's finished.
The patchset add core mesa, gallium,
From: Dave Airlie
This just adds the basic boilerplate support.
Signed-off-by: Dave Airlie
---
src/compiler/glsl/glcpp/glcpp-parse.y| 3 +++
src/compiler/glsl/glsl_parser_extras.cpp | 1 +
src/compiler/glsl/glsl_parser_extras.h | 7 +++
3
Am 08.06.2016 um 14:20 schrieb Julien Isorce:
On 8 June 2016 at 09:16, Christian König > wrote:
Am 02.06.2016 um 16:00 schrieb Julien Isorce:
In order to do zero-copy between two different devices
the memory
In tree build make distclean is failing for me since -
b7f7ec78435771ab02f7d9a61bb1d4a11df720b8 is the first bad commit
commit b7f7ec78435771ab02f7d9a61bb1d4a11df720b8
Author: Emil Velikov
Date: Mon Jun 6 19:39:40 2016 +0100
mesa: automake: distclean
Am 02.06.2016 um 16:00 schrieb Julien Isorce:
In order to do zero-copy between two different devices
the memory should not be tiled.
This is currently no way to set pipe_resource template's flag
from pipe_video_buffer template. So disabled_tiling is added.
Choosed "disable" prefix so that
Am 02.06.2016 um 16:03 schrieb Julien Isorce:
Signed-off-by: Julien Isorce
Actually I'm not sure if that is correct.
If you release the VABuffer of an exported resource you won't be able to
properly close the handle with vlVaReleaseBufferHandle().
On the other hand
Am 02.06.2016 um 16:03 schrieb Julien Isorce:
Instead of changing the format on the existing template
which makes error handling not nice and confuses coverity.
CoverityID: 1337953
Signed-off-by: Julien Isorce
Reviewed-by: Christian König
Am 07.06.2016 um 19:42 schrieb Nayan Deshmukh:
Apply the luma key filter to the YCbCr values during the CSC conversion
in video buffer shader. The initial values of max and min luma are set
to opposite values to disable the filter initially and will be set when
enabling it.
Add extra parmeters
https://bugs.freedesktop.org/show_bug.cgi?id=96408
--- Comment #2 from gregory.hain...@gmail.com ---
Hum, when a new program is set, use_shader_program is called and the
_NEW_PROGRAM flag will be set.
use_shader_program()
{
if (*target != shProg) {
/* Program is current, flush
Apply the luma key filter to the YCbCr values during the CSC conversion
in video buffer shader. The initial values of max and min luma are set
to opposite values to disable the filter initially and will be set when
enabling it.
Add extra parmeters min and max luma for the luma
Signed-off-by: Nayan Deshmukh
---
src/gallium/state_trackers/vdpau/mixer.c | 45 ++--
src/gallium/state_trackers/vdpau/vdpau_private.h | 6 +++-
2 files changed, 39 insertions(+), 12 deletions(-)
diff --git
AFAIK the term is "luma keying", not "luma keyring".
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
___
mesa-dev mailing list
Signed-off-by: Nayan Deshmukh
---
src/gallium/state_trackers/vdpau/mixer.c | 45 ++--
src/gallium/state_trackers/vdpau/vdpau_private.h | 6 +++-
2 files changed, 39 insertions(+), 12 deletions(-)
diff --git
Hi Christian,
Thx for the review.
pipe_resource_reference(, NULL) will decrement reference counting
(p_atomic_dec res->count). But the va surface still has the initial
reference since it created that resource.
So calling vaDestroyImage on a derived image will call VaDestroyBuffer but
the
With the type fixed both patches are Reviewed-by: Christian König
If there aren't any more objections I'm going to push the patches now.
Regards,
Christian.
Am 08.06.2016 um 11:28 schrieb Michel Dänzer:
AFAIK the term is "luma keying", not "luma keyring".
I'm clearly not deep enough into VA-API to judge if that is correct or
not, but it sounds sane to me.
So feel free to add an Acked-by: Christian König
on the patch.
Cheers,
Christian.
Am 08.06.2016 um 13:13 schrieb Julien Isorce:
Hi Christian,
Thx for the
Hello
Mesa 12.1.0-devel (git-8c3ecde) has rendering issues when running
"glxgears -samples N" with N >= 1 on R9 390. It was running ok
yesterday/previously.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
On 8 June 2016 at 09:16, Christian König wrote:
> Am 02.06.2016 um 16:00 schrieb Julien Isorce:
>
>> In order to do zero-copy between two different devices
>> the memory should not be tiled.
>>
>> This is currently no way to set pipe_resource template's flag
>> from
> On Jun 7, 2016, at 03:25, Emil Velikov wrote:
>
> On 31 May 2016 at 10:53, Tapani Pälli wrote:
>> From: Daniel Czarnowski
>>
>> GLX documentation states:
>>glXCreateNewContext can generate the following
From: Dave Airlie
This is prep work for int64 support.
Signed-off-by: Dave Airlie
---
src/compiler/glsl/link_varyings.cpp | 2 +-
src/compiler/glsl/link_varyings.h | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git
On Jun 8, 2016 9:25 PM, "Kristian Høgsberg" wrote:
>
> On Wed, Jun 8, 2016 at 9:07 PM, Jason Ekstrand
wrote:
> > When Kristian implemented GL_TEXTURE_EXTERNAL_OES, he hooked it up for
gen8
> > but not for gen7 or earlier. It all works, we just need to
To go back to "add a bind flag to struct pipe_video_buffer instead ", the
alternative is to bring back the first version
of the patch but according to the first review, it was duplication of bind
flag between pipe_video_buffer
and pipe_resource so it would require quite of big of refactoring
Am 08.06.2016 um 15:53 schrieb Julien Isorce:
To go back to "add a bind flag to struct pipe_video_buffer instead ",
the alternative is to bring back the first version
of the patch but according to the first review, it was duplication of
bind flag between pipe_video_buffer
and pipe_resource so
When Kristian implemented GL_TEXTURE_EXTERNAL_OES, he hooked it up for gen8
but not for gen7 or earlier. It all works, we just need to emit the states
for the extra planes.
Cc: "12.0"
Cc: Kristian Høgsberg
---
When Kristian implemented GL_TEXTURE_EXTERNAL_OES, he hooked it up for gen8
but not for gen7 or earlier. It all works, we just need to emit the states
for the extra planes.
Cc: "12.0"
Cc: Kristian Høgsberg
---
On Wed, Jun 8, 2016 at 9:07 PM, Jason Ekstrand wrote:
> When Kristian implemented GL_TEXTURE_EXTERNAL_OES, he hooked it up for gen8
> but not for gen7 or earlier. It all works, we just need to emit the states
> for the extra planes.
Ah yes, thanks.
Reviewed-by: Kristian
Since this extension allows more than one varying to share a single
location we can't just count the number of slots a varying takes and
add it to the total.
Instead we now reuse the reserved varyings bitfield to determine how
many slots are reserved for explicit locations instead.
---
From: Mathias Fröhlich
The functions are also useful for mesa.
Introduce src/util/bitscan.{h,c}. Move ffs function
implementations from src/mesa/main/imports.{h,c}.
Move bit scan related functions from
src/gallium/auxiliary/util/u_math.h. Merge platform
handling with
From: Mathias Fröhlich
Hi all,
I just put the two leading patches to move u_bit_scan
from gallium to util. The architecture handling of
ffs{,ll} is merged with what is available in the
mesa/util directory. It compiles and works here and
we should get slightly better
From: Mathias Fröhlich
Signed-off-by: Mathias Fröhlich
---
src/mesa/main/arrayobj.c | 6 +++---
src/mesa/main/buffers.c | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/src/mesa/main/arrayobj.c
On Wednesday, June 8, 2016 7:45:43 PM PDT Alejandro Piñeiro wrote:
> On 02/06/16 23:09, Kenneth Graunke wrote:
> > i965 has no special hardware for this, so the best way to implement
> > this is to pass it in via a uniform.
>
> Is this comment accurate? On the next patch you implement the i965
1 - 100 of 103 matches
Mail list logo