On Fri, Mar 15, 2019 at 3:46 PM Ilia Mirkin wrote:
>
> On Fri, Mar 15, 2019 at 10:29 AM Alyssa Rosenzweig
wrote:
> >
> > > This is needed if you can only handle point sprites on certain
> > > varyings but not others. This is the case for nv30- and nvc0-based
> > > GPUs, which is why the cap was
https://bugs.freedesktop.org/show_bug.cgi?id=110116
--- Comment #6 from QwertyChouskie ---
Created attachment 143684
--> https://bugs.freedesktop.org/attachment.cgi?id=143684=edit
Neverball apitrace
Here's an apitrace from my system with the Ubuntu 18.04, Mesa 18.3.3, and
Neverball 1.6.0 from
On Fri, Mar 15, 2019 at 11:52 AM Connor Abbott wrote:
>
> On Fri, Mar 15, 2019 at 3:46 PM Ilia Mirkin wrote:
> >
> > On Fri, Mar 15, 2019 at 10:29 AM Alyssa Rosenzweig
> > wrote:
> > >
> > > > This is needed if you can only handle point sprites on certain
> > > > varyings but not others. This
On Thu, 14 Mar 2019 at 10:41, Chema Casanova wrote:
>
> On 13/3/19 23:17, Emil Velikov wrote:
> > Hi Jose,
> >
> > On Wed, 21 Nov 2018 at 18:45, Jose Maria Casanova Crespo
> > wrote:
> >>
> >> Fixes:
> >> KHR-GLES*.core.tessellation_shader.single.xfb_captures_data_from_correct_stage
> >>
> >
Hello list,
The candidate for the Mesa 18.3.5 is now available. Currently we have:
- 67 queued
- 0 nominated (outstanding)
- and 6 rejected patches
Take a look at section "Mesa stable queue" for more information.
Testing reports/general approval
Any testing
https://bugs.freedesktop.org/show_bug.cgi?id=110116
--- Comment #5 from QwertyChouskie ---
According to
https://github.com/Neverball/neverball/issues/170#issuecomment-473301333 there
seems to be some difference between the Debian/Ubuntu packaged Neverball and
building it from source. Also, the
On 14/03/2019 19:37, Brian Paul wrote:
When st_texture_release_all_sampler_views() is called the texture may
have sampler views belonging to several contexts. If we unreference a
sampler view and its refcount hits zero, we need to be sure to destroy
the sampler view with the same context which
On Fri, Mar 15, 2019 at 5:00 PM Ilia Mirkin wrote:
>
> On Fri, Mar 15, 2019 at 11:52 AM Connor Abbott
wrote:
> >
> > On Fri, Mar 15, 2019 at 3:46 PM Ilia Mirkin
wrote:
> > >
> > > On Fri, Mar 15, 2019 at 10:29 AM Alyssa Rosenzweig <
aly...@rosenzweig.io> wrote:
> > > >
> > > > > This is needed
Am 15.03.2019 15:20, schrieb Samuel Pitoiset:
Results of my benchmarks are:
3 runs at 1080p:
GFX8: -1%
GFX9: -1.12%
3 runs at 4k:
GFX8: -2%
GFX9: -1.85%
I'm actually not sure if we want to remove it...
Yes, my hint is we should wait until Marek is back from vacation.
Running all the
https://bugs.freedesktop.org/show_bug.cgi?id=35268
makep...@firemail.cc changed:
What|Removed |Added
CC||makep...@firemail.cc
--
You are
> So you have to be able to generate both S,T and S,1-T. [Or
> perhaps there's an explicit control for it, I forget.] With GLES2+,
> it's just gl_PointCoord though.
FWIW, the blob emits a linear (er, affine technically?) transformation
in the shader to do the flip, loading the matrix from a
>
> /home/teqdiligent/sources/xorg/git/mesa/mesa/src/intel/tools/aub_mem.c: In
> function 'memfd_create':
> /home/teqdiligent/sources/xorg/git/mesa/mesa/src/intel/tools/aub_mem.c:37:19:
> error: 'SYS_memfd_create' undeclared (first use in this function)
>
On Fri, Mar 15, 2019 at 3:49 AM Axel Davy wrote:
>
> On 15/03/2019 03:12, Rob Clark wrote:
> > On Thu, Mar 14, 2019 at 9:58 PM Roland Scheidegger
> > wrote:
> >> Am 15.03.19 um 02:18 schrieb Rob Clark:
> >>> On Thu, Mar 14, 2019 at 8:28 PM Roland Scheidegger
> >>> wrote:
> Am 14.03.19 um
On 15/03/2019 13:12, Rob Clark wrote:
On Fri, Mar 15, 2019 at 3:49 AM Axel Davy wrote:
On 15/03/2019 03:12, Rob Clark wrote:
On Thu, Mar 14, 2019 at 9:58 PM Roland Scheidegger wrote:
Am 15.03.19 um 02:18 schrieb Rob Clark:
On Thu, Mar 14, 2019 at 8:28 PM Roland Scheidegger wrote:
Am
On Fri, Mar 15, 2019 at 8:21 AM Axel Davy wrote:
> This is compatible with what I said. Nouveau determines the minimum
> number of samplers actually needed
> by the current shader, and internally unbinds those above (and rebinds
> if needed by new shader).
The things nouveau does today aren't
On Fri, Mar 15, 2019 at 8:21 AM Axel Davy wrote:
>
> On 15/03/2019 13:12, Rob Clark wrote:
> > On Fri, Mar 15, 2019 at 3:49 AM Axel Davy wrote:
>
> >> To my knowledge, the semantic of set_sampler_views was changed two years
> >> ago, and that caused some issues:
> >>
https://bugs.freedesktop.org/show_bug.cgi?id=109354
Eric Engestrom changed:
What|Removed |Added
Assignee|mesa-dev@lists.freedesktop. |fdo-b...@engestrom.ch
https://bugs.freedesktop.org/show_bug.cgi?id=110116
--- Comment #1 from Tapani Pälli ---
I've briefly tested, stars render OK on HSW but are displayed as rectangles on
KBL.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the
This is needed for lima gp compiler.
Signed-off-by: Qiang Yu
---
src/compiler/nir/nir_intrinsics.py| 4 +--
src/compiler/nir/nir_lower_io.c | 2 +-
src/compiler/nir/nir_lower_io_to_scalar.c | 41 +--
3 files changed, 42 insertions(+), 5 deletions(-)
diff
This is for the case that user only know a max size
it wants to append to the array and enlarge the array
capacity before writing into it.
Signed-off-by: Qiang Yu
---
src/util/u_dynarray.h | 19 +++
1 file changed, 15 insertions(+), 4 deletions(-)
diff --git
From: Rob Herring
Enable using lima for KMS renderonly. This still needs KMS driver
name mapping to kmsro to be used automatically.
Signed-off-by: Rob Herring
Signed-off-by: Qiang Yu
---
meson.build | 4 ++--
Signed-off-by: Qiang Yu
---
include/drm-uapi/drm_fourcc.h | 31 ++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/include/drm-uapi/drm_fourcc.h b/include/drm-uapi/drm_fourcc.h
index bab20298f42..56f737af8ca 100644
--- a/include/drm-uapi/drm_fourcc.h
From: Erico Nunes
pipe_draw_info has min_index and max_index fields that can be useful in
indexed drawing, however gallium may decide to not compute them in some
cases to avoid impacting performance if the driver won't need them.
However, some drivers may need to always compute these values to
Signed-off-by: Qiang Yu
---
src/util/u_math.h | 31 +++
1 file changed, 31 insertions(+)
diff --git a/src/util/u_math.h b/src/util/u_math.h
index e7dbbe5ca22..ffadfb47282 100644
--- a/src/util/u_math.h
+++ b/src/util/u_math.h
@@ -389,6 +389,37 @@ float_to_ubyte(float
Signed-of-by: Qiang Yu
---
include/drm-uapi/lima_drm.h | 169
1 file changed, 169 insertions(+)
create mode 100644 include/drm-uapi/lima_drm.h
diff --git a/include/drm-uapi/lima_drm.h b/include/drm-uapi/lima_drm.h
new file mode 100644
index
From: Rob Herring
Signed-off-by: Rob Herring
Signed-off-by: Qiang Yu
---
src/gallium/targets/dri/meson.build | 2 ++
src/gallium/targets/dri/target.c| 2 ++
2 files changed, 4 insertions(+)
diff --git a/src/gallium/targets/dri/meson.build
b/src/gallium/targets/dri/meson.build
index
Mesa Gallium3D driver for ARM Mali 400/450 GPUs.
Lima is still in development and not ready for daily usage,
but can run some simple tests like kmscube and glamrk2, and some
single full screen application like kodi-gbm.
Mesa related EGL/GLX_EXT_buffer_age and EGL_KHR_partial_update
changes are
On Fri, Mar 15, 2019 at 8:55 AM Jose Fonseca wrote:
>
> On 14/03/2019 19:37, Brian Paul wrote:
> > When st_texture_release_all_sampler_views() is called the texture may
> > have sampler views belonging to several contexts. If we unreference a
> > sampler view and its refcount hits zero, we need
On 16/3/19 6:53 am, Dieter Nützel wrote:
Am 15.03.2019 15:20, schrieb Samuel Pitoiset:
Results of my benchmarks are:
3 runs at 1080p:
GFX8: -1%
GFX9: -1.12%
3 runs at 4k:
GFX8: -2%
GFX9: -1.85%
I'm actually not sure if we want to remove it...
Yes, my hint is we should wait until Marek
On 03/15/2019 09:54 AM, Jose Fonseca wrote:
On 14/03/2019 19:37, Brian Paul wrote:
When st_texture_release_all_sampler_views() is called the texture may
have sampler views belonging to several contexts. If we unreference a
sampler view and its refcount hits zero, we need to be sure to destroy
When st_texture_release_all_sampler_views() is called the texture may
have sampler views belonging to several contexts. If we unreference a
sampler view and its refcount hits zero, we need to be sure to destroy
the sampler view with the same context which created it.
This was not the case with
Hello Sir,
This Is Milav Soni From TEQ DILIGENT.
I cross compiled the xserver using jhbuild.
I follow the following link.
https://www.x.org/wiki/CrossCompilingXorg/
But when it comes in mesa configuration, it gives following error.
This fixes a rendering issue with Hellblade and DXVK.
Fixes: a66b186bebf ("radv: use typed buffer loads for vertex input fetches")
Reported-by: Philip Rebohle
Signed-off-by: Samuel Pitoiset
---
src/amd/vulkan/radv_nir_to_llvm.c | 23 ++-
1 file changed, 14 insertions(+), 9
On 15/03/2019 03:12, Rob Clark wrote:
On Thu, Mar 14, 2019 at 9:58 PM Roland Scheidegger wrote:
Am 15.03.19 um 02:18 schrieb Rob Clark:
On Thu, Mar 14, 2019 at 8:28 PM Roland Scheidegger wrote:
Am 14.03.19 um 22:06 schrieb Rob Clark:
On Thu, Mar 14, 2019 at 3:58 PM Roland Scheidegger
Am 16.03.19 um 02:28 schrieb Qiang Yu:
> Signed-off-by: Qiang Yu
> ---
> src/util/u_math.h | 31 +++
> 1 file changed, 31 insertions(+)
>
> diff --git a/src/util/u_math.h b/src/util/u_math.h
> index e7dbbe5ca22..ffadfb47282 100644
> --- a/src/util/u_math.h
> +++
On Sat, Mar 16, 2019 at 09:28:48AM +0800, Qiang Yu wrote:
> This is for the case that user only know a max size
> it wants to append to the array and enlarge the array
> capacity before writing into it.
>
> Signed-off-by: Qiang Yu
> ---
> src/util/u_dynarray.h | 19 +++
> 1 file
https://bugs.freedesktop.org/show_bug.cgi?id=110116
--- Comment #3 from Denis ---
hi, I also checked on KBL and HSW. Don't see this issue (KBL was launched under
X, mesa-git from master, for HSW I installed gnome and launched under wayland).
GL renderer: Mesa DRI Intel(R) Haswell Mobile
GL
https://bugs.freedesktop.org/show_bug.cgi?id=110116
--- Comment #4 from Denis ---
update - checked and 18.3.3 mesa version (built from git). Also works fine
(HSW).
HSW on X (mesa 18.3.4) also doesn't reproduce the issue
--
You are receiving this mail because:
You are the assignee for the bug.
This was added in 8a7d4092d260 but no longer seems to have any
impact on performance.
---
src/amd/vulkan/radv_device.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/src/amd/vulkan/radv_device.c b/src/amd/vulkan/radv_device.c
index 9570c15af02..56421dbc74b 100644
On 3/14/19 1:26 PM, Milav wrote:
Hello Sir,
This Is Milav Soni From TEQ DILIGENT.
I cross compiled the xserver using jhbuild.
I follow the following link.
https://www.x.org/wiki/CrossCompilingXorg/
But when it comes in mesa configuration, it gives following error.
On Thu, 14 Mar 2019 20:00:45 -0500
Jason Ekstrand wrote:
> >
> > extern const struct anv_dynamic_state default_dynamic_state;
> > diff --git a/src/intel/vulkan/genX_cmd_buffer.c
> > b/src/intel/vulkan/genX_cmd_buffer.c
> > index 7687507e6b7..5d2b17cf8ae 100644
> > ---
https://bugs.freedesktop.org/show_bug.cgi?id=110116
--- Comment #2 from Ilia Mirkin ---
Seems to work with llvmpipe on 19.0-rc7. (And with nouveau on multiple GPU
generations.)
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the
This is needed if you can only handle point sprites on certain
varyings but not others. This is the case for nv30- and nvc0-based
GPUs, which is why the cap was introduced.
If your GPU does not have such restrictions, you can safely remove the cap.
-ilia
On Fri, Mar 15, 2019 at 12:25 AM
On Friday, 2019-03-15 21:25:33 +1100, Timothy Arceri wrote:
> This was added in 8a7d4092d260 but no longer seems to have any
> impact on performance.
> ---
> src/amd/vulkan/radv_device.c | 10 +-
> 1 file changed, 1 insertion(+), 9 deletions(-)
>
> diff --git
Results of my benchmarks are:
3 runs at 1080p:
GFX8: -1%
GFX9: -1.12%
3 runs at 4k:
GFX8: -2%
GFX9: -1.85%
I'm actually not sure if we want to remove it...
On 3/15/19 11:25 AM, Timothy Arceri wrote:
This was added in 8a7d4092d260 but no longer seems to have any
impact on performance.
---
> This is needed if you can only handle point sprites on certain
> varyings but not others. This is the case for nv30- and nvc0-based
> GPUs, which is why the cap was introduced.
>
> If your GPU does not have such restrictions, you can safely remove the cap.
Ah-ha, I see, thank you.
I can't
There is no BO tracking for vertex buffers yet, so it is not safe to
directly map even when we can according to alignment restrictions. For
now, always create a shadow buffer.
Signed-off-by: Alyssa Rosenzweig
---
src/gallium/drivers/panfrost/pan_context.c | 5 -
1 file changed, 4
On Fri, Mar 15, 2019 at 10:29 AM Alyssa Rosenzweig wrote:
>
> > This is needed if you can only handle point sprites on certain
> > varyings but not others. This is the case for nv30- and nvc0-based
> > GPUs, which is why the cap was introduced.
> >
> > If your GPU does not have such restrictions,
48 matches
Mail list logo
