On Fri, 2018-08-31 at 14:48 -0700, Chad Versace wrote:
> On Fri 31 Aug 2018, Jason Ekstrand wrote:
> > We had the flush/stall after the clear but missed the one that needs to
> > go before the clear.
> >
IIUC, Chad has given a R+1 to this. So I think this patch can be pushed, right?
On Tue, 2018-09-11 at 11:15 -0500, Jason Ekstrand wrote:
> Cc: mesa-sta...@lists.freedesktop.org
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107892
> ---
> src/mesa/drivers/dri/i965/brw_meta_util.c | 3 +++
> 1 file changed, 3 insertions(+)
>
This has been reviewed, but not pushed
On Mon, 2018-09-24 at 13:33 -0700, Dylan Baker wrote:
> Quoting Chuck Atkins (2018-09-24 13:24:29)
> > Hi Dylan,
> >
> >
> > I think you could simplify this:
> >
> > > + if dep_llvm.found() and with_gallium_swr and dep_llvm.version
> > ().version_compare('>= 7')
> > > +
On Wed, 2018-08-29 at 18:13 +0100, Emil Velikov wrote:
> From: Emil Velikov
>
> As the newly introduced comment says:
> The pipe loader takes ownership of the fd
>
> Thus, there's no need to close it again.
This patch seems to be already reviewed, but not pushed to upstream.
J.A.
On Mon, 2018-09-24 at 20:21 -0400, Marek Olšák wrote:
> Looks good to me.
>
> Marek
This patch was nominated to stable, but I can't apply it on 18.2 because this
patch requires 98f777f9d9c ("radeonsi: remove fetch_args callbacks for ALU
instructions"), which was not nominated.
WDYT? Should both
On 9/28/18 10:53 PM, Bas Nieuwenhuizen wrote:
On Fri, Sep 28, 2018 at 4:27 PM Samuel Pitoiset
wrote:
Like we disable DCC/CMASK for small color surfaces as well.
Serious Sam 2017 creates a 1x1 depth surface and I think
it should be faster to decompress compared to the benefit
of fast clears.
On Mon, 2018-09-03 at 13:05 +0100, Emil Velikov wrote:
> From: Emil Velikov
>
> Analogous to the previous commit - the spec says the function is a
> no-op when a pbuffer or pixmap surface is used.
>
This series seems to be reviewed, but not pushed yet in master.
J.A.
> Cc: samiuddi
maybe also move the declaration of ret closer to the actual usage in
anv_wait_for_bo_fences?
Reviewed-by: Tapani Pälli
On 9/30/18 9:12 PM, Bas Nieuwenhuizen wrote:
All three are only used in asserts, so this silences release build
warnings.
---
src/intel/vulkan/anv_blorp.c | 3 ++-
From ARB_gl_spirv:
"Mapping of layouts
std140/std430 -> explicit *Offset*, *ArrayStride*, and *MatrixStride*
Decoration on struct members"
That means that we would not have available any kind of layout info,
and we should use explicit array strides.
This
Hi all,
Once more huge thanks to the entire team from g.p.u.l. and Igalia,
personally I think this was an extremely well organized XDC!
As usual we're looking for feedback on both XDC itself, and the CFP
process and program selection. Both about what was great and should be
kept for next year's
Fixed pack_uint_Z_FLOAT32 by casting row data to float instead uint.
Remove code duplicate function pack_uint_Z_FLOAT32_X24S8.
Edited case in "_mesa_get_pack_uint_z_func".
Now it looks like "_mesa_get_pack_float_z_func".
v2: by Nanley Chery
-add coments
-remove _mesa_problem call, which was added
I already edited the patch, just waiting on the Intel devs to consider the
SWR code changes that go with this.
- Chuck
On Mon, Oct 1, 2018 at 11:26 AM Dylan Baker wrote:
> Quoting Juan A. Suarez Romero (2018-10-01 01:56:25)
> > On Mon, 2018-09-24 at 13:33 -0700, Dylan Baker wrote:
> > >
On Monday, 2018-10-01 11:04:09 +0200, Juan A. Suarez Romero wrote:
> On Tue, 2018-09-11 at 11:15 -0500, Jason Ekstrand wrote:
> > Cc: mesa-sta...@lists.freedesktop.org
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107892
> > ---
> > src/mesa/drivers/dri/i965/brw_meta_util.c | 3 +++
>
Quoting Juan A. Suarez Romero (2018-10-01 01:56:25)
> On Mon, 2018-09-24 at 13:33 -0700, Dylan Baker wrote:
> > Quoting Chuck Atkins (2018-09-24 13:24:29)
> > > Hi Dylan,
> > >
> > >
> > > I think you could simplify this:
> > >
> > > > + if dep_llvm.found() and with_gallium_swr and
From: suresh guttula
In case of decoding of resolution like 40x24, while allocating surface
video buffer is always aligned with macroblock width/height which is 16.
But when application tries to get data after decoding through vaCreateImage
/vaGetImage, image width/height aligned with 2 and
The patch I attached was written for 18.2. It won't apply on master.
It looks the same, but the change is in a different function.
Marek
On Mon, Oct 1, 2018 at 6:25 PM Juan A. Suarez Romero
wrote:
>
> On Mon, 2018-10-01 at 14:29 -0400, Marek Olšák wrote:
> > The attached patch is for 18.2.
> >
16 was considering UVD.
in vlVagetImage, the width,height passed to function is not used but rather the
surface width/height and that causes issue in this case,not sure how driver
will handle that ?
From: Ilia Mirkin
Sent: Monday, October 1, 2018 6:49 PM
To:
On Mon, 2018-10-01 at 14:29 -0400, Marek Olšák wrote:
> The attached patch is for 18.2.
>
Not sure if I've explained myself correctly
The patch you're attaching is the same as 0d495bec25b ("radeonsi: NaN should
pass kill_if"), which is already in master and CCed to stable.
But in order
https://bugs.freedesktop.org/show_bug.cgi?id=107991
--- Comment #10 from Rob Stolarz ---
Created attachment 141828
--> https://bugs.freedesktop.org/attachment.cgi?id=141828=edit
apitrace using twilight princess
--
You are receiving this mail because:
You are the QA Contact for the bug.
You
This fixes a bunch of Vulkan subgroup tests on little core platforms.
Fixes: 4150920b95 "intel/fs: Add a helper for emitting scan operations"
---
src/intel/compiler/brw_fs_builder.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/intel/compiler/brw_fs_builder.h
The Vulkan API was recently clarified to allow image views of different
formats to be used for rendering to the same image. Due to certain
incompatible clear-color encodings on gen7-8, we must be more careful
about which fast-clear values we allow.
Makes the following crucible test pass pre-SKL:
https://bugs.freedesktop.org/show_bug.cgi?id=107991
--- Comment #12 from Rob Stolarz ---
I added a smaller apitrace that reproduces the issue under OpenGL; I wasn't
able to use vktrace to capture the Vulkan GPU crash. vktrace seems to produce
traces that only segfault when my GPU crashes (even
On Mon, Oct 1, 2018 at 9:47 PM Sharma, Deepak wrote:
>
> From: suresh guttula
>
> In case of decoding of resolution like 40x24, while allocating surface
> video buffer is always aligned with macroblock width/height which is 16.
> But when application tries to get data after decoding through
Just a follow-up to make sure this makes it into mesa-stable.
I know the release window for 18.2.2 is coming up.
On Thu, 27 Sep 2018 at 16:32, Dave Airlie wrote:
> On Thu, 27 Sep 2018 at 15:40, Stuart Young wrote:
> >
> > Hi All,
> >
> > Can we get some feedback on this patch please?
> >
> >
https://bugs.freedesktop.org/show_bug.cgi?id=107991
--- Comment #11 from Rob Stolarz ---
Created attachment 141829
--> https://bugs.freedesktop.org/attachment.cgi?id=141829=edit
twilight princess savestate
this is a savestate of gc twilight princess running on dolphin 5.0-8775 that
reproduces
Looking at vlVaGetImage, it looks like it just copies data into the
texture -- I don't see how UVD is implicated in this. Perhaps the
transfer's stride is being set wrong? Or maybe either
u_copy_nv12_to_yv12 or util_copy_rect (or one of the functions they
call) is having trouble?
On Mon, Oct 1,
On 01/10/2018 10:13, Juan A. Suarez Romero wrote:
On Mon, 2018-09-24 at 20:21 -0400, Marek Olšák wrote:
Looks good to me.
Marek
This patch was nominated to stable, but I can't apply it on 18.2 because this
patch requires 98f777f9d9c ("radeonsi: remove fetch_args callbacks for ALU
Hi Jason,
I'm still getting crash with this patch when run conformance test in the
firefox.
Assert is triggered during following call:
glBlitFramebuffer(srcX0 = -1, srcY0 = -1, srcX1 = 2147483646, srcY1 =
2147483646, dstX0 = 0, dstY0 = 0, dstX1 = 8, dstY1 = 8, mask =
GL_COLOR_BUFFER_BIT, filter
Kabylake doesn't have such issue, but also it doesn't have
a front buffers in that case.
Coffelake can be fixed if to wait for fences if it has back-buffer.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108097
Fixes: aefac10fecc9 (loader/dri3: Only wait for back buffer fences in
https://bugs.freedesktop.org/show_bug.cgi?id=108082
--- Comment #4 from Eric Engestrom ---
(In reply to Illia from comment #3)
> I've wrote workaround for
> this issue which hides the problem, until this problem will be fixed in
> autoconf.
You can't have any logic based on the value of $CC
https://bugs.freedesktop.org/show_bug.cgi?id=108082
--- Comment #3 from Illia ---
Created attachment 141819
--> https://bugs.freedesktop.org/attachment.cgi?id=141819=edit
workaround
I've got this warning, and another one:
warning: unknown warning option '-Wno-override-init'; did you mean
On Sunday, 2018-09-30 20:03:49 +0200, Bas Nieuwenhuizen wrote:
> ---
> src/amd/vulkan/radv_device.c | 27 +++
> src/amd/vulkan/radv_extensions.py | 1 +
> 2 files changed, 28 insertions(+)
>
> diff --git a/src/amd/vulkan/radv_device.c b/src/amd/vulkan/radv_device.c
The later are sensitive to unalligned accesses on arm64[1] and we don't
need an uncached mapping here.
[1]: https://lists.freedesktop.org/archives/etnaviv/2018-September/001956.html
Signed-off-by: Guido Günther
---
src/gallium/drivers/etnaviv/etnaviv_shader.c | 2 +-
1 file changed, 1
On Sun, Sep 30, 2018 at 1:04 PM Bas Nieuwenhuizen
wrote:
> ---
> src/amd/vulkan/radv_device.c | 27 +++
> src/amd/vulkan/radv_extensions.py | 1 +
> 2 files changed, 28 insertions(+)
>
> diff --git a/src/amd/vulkan/radv_device.c b/src/amd/vulkan/radv_device.c
>
On Sun, Sep 30, 2018 at 12:29 PM Bas Nieuwenhuizen
wrote:
> On Sat, Sep 29, 2018 at 4:40 PM Jason Ekstrand
> wrote:
> >
> > ---
> > src/intel/vulkan/anv_device.c | 27 +++
> > src/intel/vulkan/anv_extensions.py | 1 +
> > 2 files changed, 28 insertions(+)
> >
> >
https://bugs.freedesktop.org/show_bug.cgi?id=108112
Bug ID: 108112
Summary: [vulkancts] some of the coherent memory tests fail.
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity:
On Mon, Oct 01, 2018 at 08:23:56PM -0500, Jason Ekstrand wrote:
> This fixes a bunch of Vulkan subgroup tests on little core platforms.
>
> Fixes: 4150920b95 "intel/fs: Add a helper for emitting scan operations"
> ---
> src/intel/compiler/brw_fs_builder.h | 2 +-
> 1 file changed, 1
On Mon, 2018-10-01 at 21:54 -0400, Marek Olšák wrote:
> The patch I attached was written for 18.2. It won't apply on master.
> It looks the same, but the change is in a different function.
>
Ouch! The patch looks almost the same indeed :)
Thanks for it. I'll add to 18.2
J.A.
> Marek
On 09/27/2018 10:01 PM, Timothy Arceri wrote:
> On 28/9/18 2:53 am, Tom Stellard wrote:
>> On 09/24/2018 11:51 PM, Samuel Pitoiset wrote:
>>>
>>>
>>> On 9/25/18 6:46 AM, Timothy Arceri wrote:
On 25/9/18 10:35 am, Marek Olšák wrote:
> Do you know what's broken in LLVM? Or is it a problem
I haven't checked in detail, but vlVaGetImage appears to ignore the
passed-in x/y/width/height parameters. What happens if e.g. you have a
1000x1000 surface, and I call
vlVaGetImage(x=10,y=10,width=1,height=1)? Shouldn't it just return me
one pixel? If this is legal, then these limits need to be
Shouldn't it be possible to use the x11 platform (+drisw)?
On Mon, Oct 1, 2018 at 3:43 PM Dylan Baker wrote:
>
> Currently mesa only supports EGL for KMS (Linux, *BSD) systems and
> Haiku, we should actually enforce this. This fixes the default build on
> MacOS.
> ---
>
> meson.build | 7 ++-
On 2018-10-01 12:37 p.m., Sergii Romantsov wrote:
> Kabylake doesn't have such issue, but also it doesn't have
> a front buffers in that case.
> Coffelake can be fixed if to wait for fences if it has back-buffer.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108097
> Fixes:
From Section 6.1.2 (Subroutines) of the GLSL 4.00 specification
"A program will fail to compile or link if any shader
or stage contains two or more functions with the same
name if the name is associated with a subroutine type."
Fixes:
* no-overloads.vert
Bugzilla:
https://bugs.freedesktop.org/show_bug.cgi?id=108109
vadym changed:
What|Removed |Added
CC||vadym.shovkoplias@globallog
On 09/29/2018 05:20 AM, Kenneth Graunke wrote:
On Monday, September 24, 2018 8:18:37 PM CEST Nicholas Kazlauskas wrote:
Applications that don't present at a predictable rate (ie. not games)
shouldn't have adaptive sync enabled. This list covers some of the
common desktop compositors, web
https://bugs.freedesktop.org/show_bug.cgi?id=108109
--- Comment #1 from vadym ---
Patch: https://patchwork.freedesktop.org/patch/254237/
--
You are receiving this mail because:
You are the assignee for the bug.___
mesa-dev mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=108109
Bug ID: 108109
Summary: [GLSL] no-overloads.vert fails
Product: Mesa
Version: 18.2
Hardware: Other
OS: All
Status: NEW
Severity: normal
From: Tomeu Vizoso
Pass the size of a resource when creating it so a backing can be kept in
the other side.
Also pass the required offset to transfer commands.
This moves vtest closer to how virtio-gpu works, making it more useful
for testing.
v2: - Use new messages for creation and
Yes, it also works
On Mon, Oct 1, 2018 at 5:24 PM Michel Dänzer wrote:
> On 2018-10-01 12:37 p.m., Sergii Romantsov wrote:
> > Kabylake doesn't have such issue, but also it doesn't have
> > a front buffers in that case.
> > Coffelake can be fixed if to wait for fences if it has back-buffer.
> >
On Mon, Oct 1, 2018 at 12:41 PM Eric Engestrom
wrote:
> On Sunday, 2018-09-30 20:03:49 +0200, Bas Nieuwenhuizen wrote:
> > ---
> > src/amd/vulkan/radv_device.c | 27 +++
> > src/amd/vulkan/radv_extensions.py | 1 +
> > 2 files changed, 28 insertions(+)
> >
> > diff
What improvement do you get from this?
Thanks,
Marek
On Fri, Sep 28, 2018 at 10:27 AM Samuel Pitoiset
wrote:
>
> Like we disable DCC/CMASK for small color surfaces as well.
> Serious Sam 2017 creates a 1x1 depth surface and I think
> it should be faster to decompress compared to the benefit
> of
The attached patch is for 18.2.
Thanks,
Marek
On Mon, Oct 1, 2018 at 4:14 AM Juan A. Suarez Romero
wrote:
>
> On Mon, 2018-09-24 at 20:21 -0400, Marek Olšák wrote:
> > Looks good to me.
> >
> > Marek
>
> This patch was nominated to stable, but I can't apply it on 18.2 because this
> patch
https://bugs.freedesktop.org/show_bug.cgi?id=108113
Bug ID: 108113
Summary: [vulkancts] r32g32b32 transfer operations not
implemented
Product: Mesa
Version: git
Hardware: Other
OS: All
Status:
https://bugs.freedesktop.org/show_bug.cgi?id=108082
--- Comment #5 from Vinson Lee ---
The warning messages do not appear with meson.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=108115
Bug ID: 108115
Summary: [vulkancts]
dEQP-VK.subgroups.vote.graphics.subgroupallequal.*
fails
Product: Mesa
Version: git
Hardware: Other
https://bugs.freedesktop.org/show_bug.cgi?id=108116
Bug ID: 108116
Summary: [vulkancts] stencil partial clear tests fail.
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
https://bugs.freedesktop.org/show_bug.cgi?id=108114
Bug ID: 108114
Summary: [vulkancts] new VK_KHR_16bit_storage tests fail.
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
On Mon, Oct 1, 2018 at 8:04 AM Tapani Pälli wrote:
>
> maybe also move the declaration of ret closer to the actual usage in
> anv_wait_for_bo_fences?
Done.
>
> Reviewed-by: Tapani Pälli
Thanks!
>
> On 9/30/18 9:12 PM, Bas Nieuwenhuizen wrote:
> > All three are only used in asserts, so this
Currently mesa only supports EGL for KMS (Linux, *BSD) systems and
Haiku, we should actually enforce this. This fixes the default build on
MacOS.
---
meson.build | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index 97693b91ecf..202f9d740d7
This commit changes one line in the XML to enable the DRM modifiers
extension and adds the resulting Vulkan header changes.
---
include/vulkan/vulkan_core.h | 68
src/vulkan/registry/vk.xml | 2 +-
2 files changed, 69 insertions(+), 1 deletion(-)
diff
The anv implementation still isn't quite complete, but we can at least
start using the structs from the real extension.
---
src/intel/vulkan/anv_extensions.py | 1 +
src/intel/vulkan/anv_formats.c | 13 ---
src/intel/vulkan/anv_image.c | 29 +++---
Future changes will be easier if we can modify it based on whether or
not we're using modifiers.
---
src/vulkan/wsi/wsi_common.c | 43 +++--
1 file changed, 22 insertions(+), 21 deletions(-)
diff --git a/src/vulkan/wsi/wsi_common.c b/src/vulkan/wsi/wsi_common.c
The DRM format modifiers extension adds a TILING_DRM_FORMAT_MODIFIER
which will be used for modifiers so we can no longer use OPTIMAL to
indicate tiled inside the driver.
---
src/intel/vulkan/anv_formats.c | 2 +-
src/intel/vulkan/anv_image.c | 6 +++---
Just because a modifier is returned for the given format, that doesn't
mean it works with all usages and flags. We need to filter the list by
calling vkGetPhysicalDeviceImageFormatProperties2.
---
src/vulkan/wsi/wsi_common.c | 32 +++-
src/vulkan/wsi/wsi_common.h | 1
Now that the DRM format modifiers extension has been released, we can move
the WSI code over to use it instead of the pseudo-extension we were using
before. There are a few small differences we have to account for but it's
not bad. This probably shouldn't land until the extension is officially
On Mon, Sep 17, 2018 at 1:51 PM Fritz Koenig wrote:
>
> In the GL_MESA_framebuffer_flip_y implementation
> _mesa_is_winsys_fbo checks were replaced with
> FlipY checks. rb->Name is also used to determine
> if a buffer is winsys.
>
> v2: Fixes annotation [for emil]
>
> Fixes: ab05dd183cc ("i965:
66 matches
Mail list logo
