Am 01.08.2018 05:56, schrieb Timothy Arceri:
On 01/08/18 13:09, Dieter Nützel wrote:
Am 31.07.2018 13:34, schrieb Timothy Arceri:
On 31/07/18 13:50, Dieter Nützel wrote:
Am 30.07.2018 05:24, schrieb Dieter Nützel:
For the series
Tested-by: Dieter Nützel
with glmark2, glxgears, UH, UV, Blen
On Mon, Jul 30, 2018 at 12:00 PM Caio Marcelo de Oliveira Filho <
caio.olive...@intel.com> wrote:
> > > > +static int
> > > > +num_arrays_in_type(const struct glsl_type *type)
> > > > +{
> > > > + int num_arrays = 0;
> > > > + while (true) {
> > > > + if (glsl_type_is_array(type) || glsl_
On 31/07/18 16:52, Bas Nieuwenhuizen wrote:
On Fri, Jul 27, 2018 at 11:40 AM, Timothy Arceri wrote:
On 27/07/18 19:10, Bas Nieuwenhuizen wrote:
On Fri, Jul 27, 2018 at 7:32 AM, Timothy Arceri
wrote:
Because this was setting image to true we would end up calling
si_load_image_desc() whe
On 01/08/18 13:09, Dieter Nützel wrote:
Am 31.07.2018 13:34, schrieb Timothy Arceri:
On 31/07/18 13:50, Dieter Nützel wrote:
Am 30.07.2018 05:24, schrieb Dieter Nützel:
For the series
Tested-by: Dieter Nützel
with glmark2, glxgears, UH, UV, Blender 2.79 and FreeCAD 0.17
on RX 580.
With UH
On Tue, Jul 31, 2018 at 3:00 PM Jason Ekstrand wrote:
> On July 31, 2018 14:54:54 Kenneth Graunke wrote:
>
> > On Tuesday, July 31, 2018 12:22:02 PM PDT Jason Ekstrand wrote:
> >> The NIR nir_lower_io_arrays_to_elements pass attempts to split I/O
> >> variables which are arrays or matrices into
Build mesa 8479 completed
Commit 157c6e8195 by Marek Olšák on 8/1/2018 2:50 AM:
util: don't use __builtin_clz unconditionally\n\nThis fixes the build if __builtin_clz is unsupported.\n\nReviewed-by: Roland Scheidegger
Configure your notification pref
This series is:
Reviewed-by: Gurchetan Singh
On Tue, Jul 31, 2018 at 3:29 PM Dave Airlie wrote:
>
> From: Dave Airlie
>
> This hooks up compute shader creation and launch grid support.
> ---
> src/gallium/drivers/virgl/virgl_context.c | 55 ++--
> src/gallium/drivers/v
Am 01.08.2018 um 04:54 schrieb Marek Olšák:
> From: Marek Olšák
>
> This fixes the build if __builtin_clz is unsupported.
> ---
> src/util/half_float.c | 12 +++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/src/util/half_float.c b/src/util/half_float.c
> index 588
On Fri, Oct 20, 2017 at 4:34 PM, Andres Rodriguez wrote:
> When WAVE_LIMIT is set, a submission will opt-in for SPI based resource
> scheduling. Because this mechanism is cooperative, we must ensure that
> all submissions have this field set, otherwise they will bypass resource
> arbitration.
>
>
Am 31.07.2018 13:34, schrieb Timothy Arceri:
On 31/07/18 13:50, Dieter Nützel wrote:
Am 30.07.2018 05:24, schrieb Dieter Nützel:
For the series
Tested-by: Dieter Nützel
with glmark2, glxgears, UH, UV, Blender 2.79 and FreeCAD 0.17
on RX 580.
With UH I saw some small light blue triangles sp
From: Marek Olšák
This fixes the build if __builtin_clz is unsupported.
---
src/util/half_float.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/src/util/half_float.c b/src/util/half_float.c
index 588f050d924..2eff2c84f51 100644
--- a/src/util/half_float.c
+++ b
So you mean like the xorg way (priority low -> high):
/usr/share/drirc.d/xxx.conf /etc/drirc.d/xxx.conf /etc/drirc ~/.drirc
OK, I'll add this for the ease of driver config.
Regards,
Qiang
From: Adam Jackson
Sent: Wednesday, August 1, 2018 2:08:54 AM
To:
Good idea. But adding a new device attribute seems over-kill, how
about just use the driver attribute and prefix a "k:" for kernel driver
like this: ?
Regards,
Qiang
From: Michel Dänzer
Sent: Tuesday, July 31, 2018 9:35:09 PM
To: Yu, Qiang
Cc: mesa-dev@l
https://bugs.freedesktop.org/show_bug.cgi?id=107439
Bug ID: 107439
Summary: mesa defines likely/unlikely and these are C++20
keywords
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NE
"Juan A. Suarez Romero" writes:
> CXXLDgallium_dri.la
> ../../../../src/gallium/drivers/vc4/.libs/libvc4.a(vc4_cl_dump.o): In
> function `vc4_dump_cl':
> src/gallium/drivers/vc4/vc4_cl_dump.c:45: undefined reference to
> `clif_dump_init'
> src/gallium/drivers/vc4/vc4_cl_dump.c:82: undefin
I guess you guys may want to look into Ken's comments on patch 3. But
otherwise the series looks good to me and is:
Reviewed-by: Timothy Arceri
On 01/08/18 05:22, Jason Ekstrand wrote:
---
src/intel/compiler/brw_nir.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/
On Mon, 2018-07-23 at 19:52 -0400, Marek Olšák wrote:
> From: Marek Olšák
>
> ---
> src/mesa/Makefile.sources |2 +
> src/mesa/main/formats.c| 42 +
> src/mesa/main/formats.h|3 +
> src/mesa/main/texcompress_astc.cpp | 1871
Am 24.07.2018 um 01:52 schrieb Marek Olšák:
> From: Marek Olšák
>
> +uint16_t _mesa_uint16_div_64k_to_half(uint16_t v)
> +{
> + /* Zero or subnormal. Set the mantissa to (v << 8) and return. */
> + if (v < 4)
> + return v << 8;
> +
> + /* Count the leading 0s in the uint16_t */
> + i
From: Dave Airlie
This hooks up compute shader creation and launch grid support.
---
src/gallium/drivers/virgl/virgl_context.c | 55 ++--
src/gallium/drivers/virgl/virgl_encode.c | 25 -
src/gallium/drivers/virgl/virgl_encode.h | 3 ++
src/gallium/driver
From: Dave Airlie
We enable this if the host exposes glsl 430 since that indicates
the host side has robustness support.
---
src/gallium/drivers/virgl/virgl_hw.h | 1 +
src/gallium/drivers/virgl/virgl_screen.c | 3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/src/gallium
From: Dave Airlie
This uses new protocol to send the default sizes to the host.
---
src/gallium/drivers/virgl/virgl_encode.c | 6 ++
src/gallium/drivers/virgl/virgl_hw.h | 1 +
src/gallium/drivers/virgl/virgl_protocol.h | 10 ++
src/gallium/drivers/virgl/virgl_screen.c |
Build mesa 8475 failed
Commit 55d56dd859 by Marek Olšák on 7/24/2018 12:07 AM:
docs: update radeonsi features and release notes
Configure your notification preferences
___
mesa-dev mailing list
mesa-dev@lis
On July 31, 2018 14:54:54 Kenneth Graunke wrote:
On Tuesday, July 31, 2018 12:22:02 PM PDT Jason Ekstrand wrote:
The NIR nir_lower_io_arrays_to_elements pass attempts to split I/O
variables which are arrays or matrices into a sequence of separate
variables. This can help link-time optimizatio
On Tuesday, July 31, 2018 12:22:02 PM PDT Jason Ekstrand wrote:
> The NIR nir_lower_io_arrays_to_elements pass attempts to split I/O
> variables which are arrays or matrices into a sequence of separate
> variables. This can help link-time optimization by allowing us to
> remove varyings at a more
On Tuesday, July 31, 2018 12:22:00 PM PDT Jason Ekstrand wrote:
> ---
> src/intel/compiler/brw_nir.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/intel/compiler/brw_nir.c b/src/intel/compiler/brw_nir.c
> index 5990427b731..17ccfa48af6 100644
> --- a/src/intel/compi
On Tue, Jul 31, 2018 at 08:29:18AM +0200, Mathias Fröhlich wrote:
> Hi Ville,
>
> > I noticed a while back that xonotic had started to misrender the gun
> > models on i915. Yesterday I bisected it down to commit 64d2a2048054
> > ("mesa: Make gl_vertex_array contain pointers to first order VAO
> >
On Tue, Jul 31, 2018 at 9:55 AM Nils Wallménius
wrote:
> Hi, sorry for the drive-by but a comment in line below
>
> Den tis 31 juli 2018 16:09Jason Ekstrand skrev:
>
>> Shader-db results on Kaby Lake:
>>
>> total instructions in shared programs: 15166953 -> 15073611 (-0.62%)
>> instructi
Otherwise, only the first vec4 of a matrix or other complex type will
get marked as flat and we'll interpolate the others. This was caught by
a dEQP test which started failing because it did a SSO vs. non-SSO
comparison. Previously, we did the interpolation wrong consistently in
both versions. H
The NIR nir_lower_io_arrays_to_elements pass attempts to split I/O
variables which are arrays or matrices into a sequence of separate
variables. This can help link-time optimization by allowing us to
remove varyings at a more granular level.
Shader-db results on Kaby Lake:
total instructions
Shader-db results on Kaby Lake:
total instructions in shared programs: 15166953 -> 15073611 (-0.62%)
instructions in affected programs: 2390284 -> 2296942 (-3.91%)
helped: 16469
HURT: 505
total loops in shared programs: 4954 -> 4951 (-0.06%)
loops in affected programs: 3 -
---
src/intel/compiler/brw_nir.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/intel/compiler/brw_nir.c b/src/intel/compiler/brw_nir.c
index 5990427b731..17ccfa48af6 100644
--- a/src/intel/compiler/brw_nir.c
+++ b/src/intel/compiler/brw_nir.c
@@ -730,7 +730,7 @@ brw_nir_l
There exist *two* queryable EGL_RENDER_BUFFER states in EGL:
eglQuerySurface(EGL_RENDER_BUFFER) and
eglQueryContext(EGL_RENDER_BUFFER).
These changes eliminate potentially very fragile code in the upcoming
EGL_KHR_mutable_render_buffer implementation.
* eglQuerySurface(EGL_RENDER_BUFFER)
The i
If set, then the config will have __DRI_ATTRIB_MUTABLE_RENDER_BUFFER,
which translates to EGL_MUTABLE_RENDER_BUFFER_BIT_KHR.
Not used yet.
---
src/gallium/state_trackers/dri/dri_screen.c | 4 ++--
src/mesa/drivers/dri/common/utils.c | 9 +++--
src/mesa/drivers/dri/common/utils.h
Define extensions DRI_MutableRenderBufferDriver and
DRI_MutableRenderBufferLoader. These are the two halves for
EGL_KHR_mutable_render_buffer.
Outside the DRI code there is one additional change. Add
gl_config::mutableRenderBuffer to match
__DRI_ATTRIB_MUTABLE_RENDER_BUFFER. Neither are used yet.
A follow-up patch enables EGL_KHR_mutable_render_buffer for Android.
This patch is separate from the Android patch because I think it's
easier to review the platform-independent bits separately.
---
src/egl/main/eglapi.c | 1 +
src/egl/main/eglconfig.c | 3 ++
src/egl/main/egldisplay.h | 1
Tested with a low-latency handwriting application on Android Nougat on
the Chrome OS Pixelbook (codename Eve) with Kabylake.
---
src/mesa/drivers/dri/i965/brw_context.c | 86 +++-
src/mesa/drivers/dri/i965/brw_context.h | 12
src/mesa/drivers/dri/i965/intel_screen.c | 13
Specifically, implement the extension DRI_MutableRenderBufferLoader.
However, the loader enables EGL_KHR_mutable_render_buffer only if the
DRI driver implements its half of the extension,
DRI_MutableRenderBufferDriver.
---
src/egl/drivers/dri2/egl_dri2.c | 38 +-
src/egl/drivers/dri2/
This pulls an 'else' block into the function's main body, making the
code easier to follow.
Without this change, the upcoming EGL_KHR_mutable_render_buffer patch
transforms dri2_make_current() into spaghetti.
---
src/egl/drivers/dri2/egl_dri2.c | 29 +++--
1 file changed,
Despite the KHR, Android is the only OS that uses this extension, as far
as I know. Essentially, it allows the app to toggle
front-buffer/back-buffer rendering using EGL.
Android requires this extension if the device advertises support for
virtual reality. No Chrome OS device yet supports Android'
Ignore this series. It's incomplete. It seems mesa-dev had hiccups last
night.
I'll resend now.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
On Tue, 2018-07-31 at 08:03 +, Yu, Qiang wrote:
> Seems the mesa driconf infrastructure is just what I need:
> https://dri.freedesktop.org/wiki/ConfigurationInfrastructure/
>
> So I can reference the loader_get_dri_config_device_id implementation
> for adding loader driver override functionali
On Mon, 2018-07-30 at 12:14 -0700, Eric Anholt wrote:
> Jon Turney writes:
>
> > Make glXChooseFBConfig properly handle the case where the only matching
> > configs have the sRGB flag set, but no sRGB attribute is specified.
> >
> > Since 6e06e281, the sRGBcapable flag is now actually compared,
On Fri, 2018-07-27 at 16:16 +0200, Olivier Fourdan wrote:
> Hi,
>
> On Thu, 26 Jul 2018 at 19:53, Eric Anholt wrote:
> >
> > Olivier Fourdan writes:
> >
> > > get_supported_modifiers() and pixmap_from_buffers() requests both
> > > expect a window as drawable, passing a pixmap will fail as the
CXXLDgallium_dri.la
../../../../src/gallium/drivers/vc4/.libs/libvc4.a(vc4_cl_dump.o): In function
`vc4_dump_cl':
src/gallium/drivers/vc4/vc4_cl_dump.c:45: undefined reference to
`clif_dump_init'
src/gallium/drivers/vc4/vc4_cl_dump.c:82: undefined reference to
`clif_dump_destroy'
../../../
Hi, sorry for the drive-by but a comment in line below
Den tis 31 juli 2018 16:09Jason Ekstrand skrev:
> Shader-db results on Kaby Lake:
>
> total instructions in shared programs: 15166953 -> 15073611 (-0.62%)
> instructions in affected programs: 2390284 -> 2296942 (-3.91%)
> helped:
https://bugs.freedesktop.org/show_bug.cgi?id=107369
--- Comment #13 from infini...@pwned.gg ---
Created attachment 140907
--> https://bugs.freedesktop.org/attachment.cgi?id=140907&action=edit
clover debug dump
Attached a dump, it's 1 out of several thousand files and compressed is 11MB.
--
Yo
Ok, we have a diagnosis of the real issue, thanks Jason. With that i
leave dealing with it to the experts. If some testing or light review
of the proper solution is needed on the modesetting-ddx side, happy to
do that.
-mario
On Tue, Jul 31, 2018 at 6:01 PM, Jason Ekstrand wrote:
> NAK.
>
> On
This patch is no good. The bug is real but this patch is insufficient.
I've got another one running through CI which I should be posting shortly.
On Tue, Jul 31, 2018 at 6:38 AM Jason Ekstrand wrote:
> Otherwise, only the first vec4 of a matrix or other complex type will
> get marked as flat an
NAK.
On SNB+, we'd like to get Y-tiling when the surface is only being used by
the compositor and reserve X-tiling for scanout surfaces. With the
modifiers negotiation framework, the X server should be able to figure out
that the window is being composited (or blitted) and request Y-tiling. If
t
At least that's what the Linux 4.18 i915 drm/kms driver
thinks, and the disagreement between kms and Mesa leads to
pageflipping failure with X-Server 1.20's dmabuf modifiers
enabled modesetting-ddx, at least as tested on a gen 7
Ivybridge system.
Signed-off-by: Mario Kleiner
---
src/mesa/drivers
On Tue, Jul 31, 2018 at 2:35 PM, Andres Gomez wrote:
> Hi Mario,
Hi Andres,
>
> Given the current patches and the talk I had yesterday in IRC with
> Daniel and Eric it seems best case scenario is that we could only have
> the 3 first patches from:
> https://patchwork.freedesktop.org/series/44671
Otherwise, only the first vec4 of a matrix or other complex type will
get marked as flat and we'll interpolate the others. This was caught by
a dEQP test which started failing because it did a SSO vs. non-SSO
comparison. Previously, we did the interpolation wrong consistently in
both versions. H
On 30/07/18 11:23, Neil Roberts wrote:
> Timothy Arceri writes:
>
>>> +
>>> + int last_vert_stage =
>>> + util_last_bit(prog->data->linked_stages &
>>> +(((1 << (MESA_SHADER_GEOMETRY + 1)) - 1) ^
>>> + ((1 << MESA_SHADER_VERTEX) - 1)));
>> Isn't this
Thanks for the quick review!
Just re-checked no regressions with Intel CI. Pushed the series to master.
On 31/07/18 13:31, Timothy Arceri wrote:
> Reviewed-by: Timothy Arceri
>
> On 31/07/18 21:16, Alejandro Piñeiro wrote:
>> FWIW, this is the only patch pending to be reviewed on the series (so
The NIR nir_lower_io_arrays_to_elements pass attempts to split I/O
variables which are arrays or matrices into a sequence of separate
variables. This can help link-time optimization by allowing us to
remove varyings at a more granular level.
Shader-db results on Kaby Lake:
total instructions
Shader-db results on Kaby Lake:
total instructions in shared programs: 15166953 -> 15073611 (-0.62%)
instructions in affected programs: 2390284 -> 2296942 (-3.91%)
helped: 16469
HURT: 505
total loops in shared programs: 4954 -> 4951 (-0.06%)
loops in affected programs: 3 -
Reviewed-by: Timothy Arceri
On 31/07/18 21:16, Alejandro Piñeiro wrote:
FWIW, this is the only patch pending to be reviewed on the series (sorry
Timothy, I used wrong patch numbers when I pinged you on IRC).
BR
On 20/07/18 17:08, Alejandro Piñeiro wrote:
---
src/compiler/shader_info.h
Hi Mario,
Given the current patches and the talk I had yesterday in IRC with
Daniel and Eric it seems best case scenario is that we could only have
the 3 first patches from:
https://patchwork.freedesktop.org/series/44671/
Landing before branching point. Not the 4/5 and 5/5 nor, it seems:
https://
Hi;
Maybe something went wrong since patches 4,6 are missing from this series?
Functionally at least propagating mutableRenderBuffer boolean from
driver to driCreateConfigs is missing.
// Tapani
On 07/31/2018 08:00 AM, Chad Versace wrote:
Despite the KHR, Android is the only OS that uses th
On 31/07/18 13:50, Dieter Nützel wrote:
Am 30.07.2018 05:24, schrieb Dieter Nützel:
For the series
Tested-by: Dieter Nützel
with glmark2, glxgears, UH, UV, Blender 2.79 and FreeCAD 0.17
on RX 580.
With UH I saw some small light blue triangles spreading around.
Have to bisect which patch set
https://bugs.freedesktop.org/show_bug.cgi?id=77449
Bug 77449 depends on bug 80018, which changed state.
Bug 80018 Summary: [HSW] Ambient occlusion glitch in Planetary Annihilation on
Intel HD4600
https://bugs.freedesktop.org/show_bug.cgi?id=80018
What|Removed |
On 2018-07-31 10:03 AM, Yu, Qiang wrote:
>
> Seems the mesa driconf infrastructure is just what I need:
> https://dri.freedesktop.org/wiki/ConfigurationInfrastructure/
>
> So I can reference the loader_get_dri_config_device_id implementation
> for adding loader driver override functionality in /e
Looks good, Patches 1-3
Reviwed-by: Gert Wollny
Am Dienstag, den 31.07.2018, 04:47 +1000 schrieb Dave Airlie:
> From: Dave Airlie
>
> v2: add max image samples support
> ---
> src/gallium/drivers/virgl/virgl_context.c | 44
> ++
> src/gallium/drivers/virgl/virg
Seems the mesa driconf infrastructure is just what I need:
https://dri.freedesktop.org/wiki/ConfigurationInfrastructure/
So I can reference the loader_get_dri_config_device_id implementation
for adding loader driver override functionality in /etc/drirc:
Thoughts?
Thanks,
Qiang
___
64 matches
Mail list logo
