On 30/08/17 11:38, Emil Velikov wrote:
On 30 August 2017 at 11:07, Lionel Landwerlin
wrote:
@@ -249,6 +249,7 @@ static mesa_format
intel_renderbuffer_format(struct gl_context * ctx, GLenum internalFormat)
{
struct brw_context *brw = brw_context(ctx);
+
On 30/08/17 11:40, Emil Velikov wrote:
On 30 August 2017 at 11:07, Lionel Landwerlin
wrote:
--- a/src/mesa/drivers/dri/i965/brw_wm_surface_state.c
+++ b/src/mesa/drivers/dri/i965/brw_wm_surface_state.c
@@ -79,6 +79,7 @@ get_isl_surf(struct brw_context *brw,
On 30 August 2017 at 11:07, Lionel Landwerlin
wrote:
> --- a/src/mesa/drivers/dri/i965/brw_wm_surface_state.c
> +++ b/src/mesa/drivers/dri/i965/brw_wm_surface_state.c
> @@ -79,6 +79,7 @@ get_isl_surf(struct brw_context *brw, struct
> intel_mipmap_tree *mt,
>
>
On 30 August 2017 at 11:07, Lionel Landwerlin
wrote:
> @@ -249,6 +249,7 @@ static mesa_format
> intel_renderbuffer_format(struct gl_context * ctx, GLenum internalFormat)
> {
> struct brw_context *brw = brw_context(ctx);
> + const struct gen_device_info
On Wed, 2017-08-30 at 11:10 +0100, Lionel Landwerlin wrote:
> You can find this series on github :
> https://github.com/djdeath/mesa/tree/wip/djdeath/drop-is-has-brw
>
> (One paches got caught by the mailing list's size limit)
>
Assuming there is no regressions on Intel CI, series is:
You can find this series on github :
https://github.com/djdeath/mesa/tree/wip/djdeath/drop-is-has-brw
(One paches got caught by the mailing list's size limit)
On 30/08/17 11:07, Lionel Landwerlin wrote:
Hi all,
Following a quick discussion on IRC, Matt reminded me we still had
some
If LLVM was fixed to do the correct thing, we could enable CONSTBUF
LOAD for LLVM 6.0 and later.
Marek
On Wed, Aug 30, 2017 at 9:18 AM, Timothy Arceri wrote:
> On 30/08/17 10:25, Marek Olšák wrote:
>>
>> I have to conclude that I don't see a way to use LOAD with CONSTBUF
Signed-off-by: Lionel Landwerlin
---
src/mesa/drivers/dri/i965/brw_context.c | 2 --
src/mesa/drivers/dri/i965/brw_context.h | 9 -
2 files changed, 11 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_context.c
Signed-off-by: Lionel Landwerlin
---
src/mesa/drivers/dri/i965/brw_context.c | 1 -
src/mesa/drivers/dri/i965/brw_context.h | 1 -
2 files changed, 2 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_context.c
b/src/mesa/drivers/dri/i965/brw_context.c
index
Signed-off-by: Lionel Landwerlin
---
src/mesa/drivers/dri/i965/brw_context.c | 1 -
src/mesa/drivers/dri/i965/brw_context.h | 1 -
2 files changed, 2 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_context.c
b/src/mesa/drivers/dri/i965/brw_context.c
index
Signed-off-by: Lionel Landwerlin
---
src/mesa/drivers/dri/i965/brw_context.c | 1 -
src/mesa/drivers/dri/i965/brw_context.h | 1 -
src/mesa/drivers/dri/i965/intel_fbo.c | 3 ++-
src/mesa/drivers/dri/i965/intel_mipmap_tree.c | 4 +++-
4 files
Signed-off-by: Lionel Landwerlin
---
src/mesa/drivers/dri/i965/brw_context.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/src/mesa/drivers/dri/i965/brw_context.h
b/src/mesa/drivers/dri/i965/brw_context.h
index 02ba0948cf8..d6fb9146129 100644
---
We need to take some take here as brw->is_broxton has been used to
check whether the device is a low power gen9 (aka Atom gen9 platform).
Signed-off-by: Lionel Landwerlin
---
src/mesa/drivers/dri/i965/brw_context.c | 1 -
Signed-off-by: Lionel Landwerlin
---
src/mesa/drivers/dri/i965/brw_context.c | 1 -
src/mesa/drivers/dri/i965/brw_context.h | 1 -
src/mesa/drivers/dri/i965/brw_misc_state.c | 3 ++-
src/mesa/drivers/dri/i965/brw_wm_surface_state.c | 7
Signed-off-by: Lionel Landwerlin
---
src/mesa/drivers/dri/i965/brw_context.c | 1 -
src/mesa/drivers/dri/i965/brw_context.h | 1 -
2 files changed, 2 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_context.c
b/src/mesa/drivers/dri/i965/brw_context.c
index
Signed-off-by: Lionel Landwerlin
---
src/mesa/drivers/dri/i965/brw_blorp.c| 2 +-
src/mesa/drivers/dri/i965/brw_context.c | 3 +--
src/mesa/drivers/dri/i965/brw_context.h | 1 -
src/mesa/drivers/dri/i965/brw_curbe.c| 2 +-
Signed-off-by: Lionel Landwerlin
---
src/mesa/drivers/dri/i965/brw_context.c | 1 -
src/mesa/drivers/dri/i965/brw_context.h | 1 -
src/mesa/drivers/dri/i965/brw_draw_upload.c | 2 +-
src/mesa/drivers/dri/i965/gen7_l3_state.c | 6 +++---
Signed-off-by: Lionel Landwerlin
---
src/mesa/drivers/dri/i965/brw_context.c | 5 ++---
src/mesa/drivers/dri/i965/brw_context.h | 1 -
src/mesa/drivers/dri/i965/brw_cs.c| 2 +-
src/mesa/drivers/dri/i965/brw_draw.c
Signed-off-by: Lionel Landwerlin
---
src/mesa/drivers/dri/i965/brw_context.c | 3 +--
src/mesa/drivers/dri/i965/brw_context.h | 1 -
src/mesa/drivers/dri/i965/genX_state_upload.c | 4 +++-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git
Signed-off-by: Lionel Landwerlin
---
src/mesa/drivers/dri/i965/brw_context.c | 1 -
src/mesa/drivers/dri/i965/brw_context.h | 2 --
src/mesa/drivers/dri/i965/brw_queryobj.c | 4 ++--
src/mesa/drivers/dri/i965/gen7_urb.c | 4 ++--
Signed-off-by: Lionel Landwerlin
---
src/mesa/drivers/dri/i965/brw_context.c| 1 -
src/mesa/drivers/dri/i965/brw_context.h| 1 -
src/mesa/drivers/dri/i965/intel_batchbuffer.c | 6 --
src/mesa/drivers/dri/i965/intel_mipmap_tree.c | 2 +-
Signed-off-by: Lionel Landwerlin
---
src/intel/vulkan/genX_pipeline.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/intel/vulkan/genX_pipeline.c b/src/intel/vulkan/genX_pipeline.c
index 83c4487bf9b..6dfa49b8737 100644
---
Hi all,
Following a quick discussion on IRC, Matt reminded me we still had
some duplicated fields on brw_context which just hold the same values
as gen_device_info. Let's just use gen_device_info instead.
Cheers,
Lionel Landwerlin (16):
anv: use device->info instead of brw->is_*
i965: drop
Hi Thomas,
Analogous to 7/8 please squash this with 2/8.
On 29 August 2017 at 20:56, Thomas Helland wrote:
> ---
> src/util/tests/string_buffer/Makefile.am | 16 ++--
> 1 file changed, 10 insertions(+), 6 deletions(-)
>
> diff --git
On 29 August 2017 at 20:56, Thomas Helland wrote:
> ---
> src/util/tests/string_buffer/append_and_print.c | 99 --
> src/util/tests/string_buffer/append_and_print.cpp | 221
> ++
> 2 files changed, 221 insertions(+), 99 deletions(-)
>
On 29 August 2017 at 20:56, Thomas Helland wrote:
> -SUBDIRS = xmlpool . tests/hash_table
> +SUBDIRS = . tests/hash_table \
> + . tests/string_buffer
>
xmlpool disappeared here and current directory (.) is seen multiple times.
To minimise this kind of issues I
Hi Thomas,
On 29 August 2017 at 20:56, Thomas Helland wrote:
> This is a resend of the string buffer implementation and
> related patches sent out back in May. I've done one more
> change to the string buffer; using u_string.h for a compatible
> vsnprintf version to
On Wed, Aug 30, 2017 at 11:19 AM, Emil Velikov wrote:
> Hi Marek,
>
> There's a couple of subtle changes in the patch. If intentional, could
> you mention that in the commit message?
>
> On 29 August 2017 at 23:25, Marek Olšák wrote:
>
>> static void
On 29 August 2017 at 04:23, Leo Liu wrote:
> Since it's no longer being called outside of compositor
>
Thanks Leo, for the split.
There's a vl_compositor_set_yuv_layer reference loose in the header.
Please remove that one with the patch, but don't bother resending.
-Emil
Hi Marek,
There's a couple of subtle changes in the patch. If intentional, could
you mention that in the commit message?
On 29 August 2017 at 23:25, Marek Olšák wrote:
> static void r600_disk_cache_create(struct r600_common_screen *rscreen)
> {
> /* Don't use the
Am 30.08.2017 um 04:49 schrieb Brian Paul:
> On 08/29/2017 06:17 PM, Roland Scheidegger wrote:
>> Looks good to me, thanks.
>>
>> Reviewed-by: Roland Scheidegger
>>
>> Albeit I'm not quite sure why it is never set here?
>
> This particular test sets a 0 x 0 scissor region.
Reviewed-by: Samuel Pitoiset
On 08/30/2017 12:25 AM, Marek Olšák wrote:
From: Marek Olšák
---
src/gallium/drivers/r600/r600_pipe.c | 2 +-
src/gallium/drivers/radeon/r600_pipe_common.c | 20 ++--
https://bugs.freedesktop.org/show_bug.cgi?id=102318
--- Comment #1 from Emil Velikov ---
Based on the error message, it seems that the HAVE_LLVM does not end up with
the correct version (0x0500).
To fix this you want to look at the way llvm_version is handled in
https://bugs.freedesktop.org/show_bug.cgi?id=102318
Alex Granni changed:
What|Removed |Added
See Also|
https://bugs.freedesktop.org/show_bug.cgi?id=100201
Alex Granni changed:
What|Removed |Added
See Also|
> btw, does lima have some way to write to memory from cmdstream (ie.
> without setting up a full blown draw)? If so perhaps you could get
> away with leaving some extra space at the end of your uniform buffer
> that you copy driver internal uniforms into before kicking the draw?
Unfortunately
On 30/08/17 10:25, Marek Olšák wrote:
I have to conclude that I don't see a way to use LOAD with CONSTBUF
and keep the same performance as before. It looks like there are some
deficiencies in our compiler stack that are unfixable in Mesa alone.
Well that's frustrating :( Pretty much makes
> In my case, VC4 has lots of custom state-dependent uniforms, and uniform
> upload is where we spend most of our CPU time (basically each draw call
> needs to re-upload the uniform stream, and the stream has to be in the
> order they will be used by instructions, rather than where they appear
>
So as a random drive-by review, I think the risk in this implementation
is that apps just set maxdrawcount to some high value . If I'm reading
the spec correctly there is no real bound on the value except for the
max-representable value for the integer. Also AFAIK the AMD and NVidia
Thanks Kenneth, here attach my RFC prototype patch implementing these,
and comments follows.
>> When working on lima gp compiler, I come across two problems about
>> inserting extra uniform
>> and instructions in nir for the driver and don't know where's the
>> right place to do it. So I'd like
Although from SPIR-V point of view, rounding modes are attached to the
operation/destination, on i965 it is a status, so we don't need to
explicitly set the rounding mode if the one we want is already set.
v2: Use a single SHADER_OPCODE_RND_MODE opcode taking an immediate
with the rounding
By default we don't set the rounding mode. We only set
round-to-near-even or round-to-zero mode if explicitly set from nir.
v2: Use a single SHADER_OPCODE_RND_MODE opcode taking an immediate
with the rounding mode (Curro)
Signed-off-by: Jose Maria Casanova Crespo
Although it is possible to emit them directly as AND/OR on brw_fs_nir,
having a specific opcode makes it easier to remove duplicate settings
later.
v2: (Curro)
- Set thread control to 'switch' when using the control register
- Use a single SHADER_OPCODE_RND_MODE opcode taking an immediate
101 - 143 of 143 matches
Mail list logo