Musl does not define __GLIBC__ and will not provide a __MUSL__ macro:
http://wiki.musl-libc.org/wiki/FAQ#Q:_why_is_there_no_MUSL_macro_.3F
This patch checks for the presence of endian.h and promotes the result
to src/amd/Makefile.addrlib.am which executes the broken build command.
Fixes compile
dri3 allows us to send handle of a texture directly to X
so this patch allows a state tracker to directly send its
texture to X to be used as back buffer and avoids extra
copying
v2: use clip width/height to display a portion of the surface
v3: remove redundant variables, fix wrapping, rename
On Sun, Oct 30, 2016 at 11:45 PM, Boyan Ding wrote:
> According to OpenGL Shading Language 4.50 spec, Section 8.7 "Vector
> Relational Functions", functions of this type do not operate on scalar
> types, so remove scalar types from signature definitions to make the
>
On 11/04/2016 03:54 PM, Leo Liu wrote:
On 11/04/2016 02:45 PM, Nayan Deshmukh wrote:
dri3 allows us to send handle of a texture directly to X
so this patch allows a state tracker to directly send its
texture to X to be used as back buffer and avoids extra
copying
v2: use clip width/height
Hi Nayan,
+ /* In case of a single gpu we need to get the
+* handle and pixmap for the texture that is set
+*/
+ if (buffer && scrn->output_texture &&
+ !scrn->is_different_gpu)
+ allocate_new_buffer = true;
+
>So now the normal case i.e. single gpu case have to
On 11/04/2016 02:45 PM, Nayan Deshmukh wrote:
dri3 allows us to send handle of a texture directly to X
so this patch allows a state tracker to directly send its
texture to X to be used as back buffer and avoids extra
copying
v2: use clip width/height to display a portion of the surface
v3:
From the Vulkan spec 1.0.32 section 29.6 docs for vkAcquireNextImageKHR:
"Let n be the total number of images in the swapchain, m be the value of
VkSurfaceCapabilitiesKHR::minImageCount, and a be the number of
presentable images that the application has currently acquired (i.e.
images
(Sorry about the top post. Sent from my phone.)
That expression will allow versions like 0130 as valid. If you just want
to allow 0, you need a more complex regular expression. I feel like that's
just a bandage... what about other bad values like "#version -130"? Won't
that have the same
On Nov 4, 2016 2:30 AM, "Pohjolainen, Topi"
wrote:
>
> On Fri, Nov 04, 2016 at 11:17:13AM +0200, Pohjolainen, Topi wrote:
> > On Fri, Oct 28, 2016 at 02:17:12AM -0700, Jason Ekstrand wrote:
> > > Previously, blorp copy operations were CCS-unaware so you had to
perform
On Fri, Nov 04, 2016 at 07:53:25PM +0100, Bernd Kuhls wrote:
> Musl does not define __GLIBC__ and will not provide a __MUSL__ macro:
> http://wiki.musl-libc.org/wiki/FAQ#Q:_why_is_there_no_MUSL_macro_.3F
>
> This patch checks for the presence of endian.h and promotes the result
> to
On Fri, 2016-11-04 at 18:43 +0100, Alejandro Piñeiro wrote:
> Nitpick: I found the commit message hard to understand until I read
> the
> summary.
Ok I'll duplicate some of the summary in the commit message.
>
> On 03/11/16 11:47, Timothy Arceri wrote:
> >
> > Since we started releasing GLSL
https://bugs.freedesktop.org/show_bug.cgi?id=98595
Bug ID: 98595
Summary: glsl: ralloc assertion "info->canary == CANARY" failed
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: OpenBSD
Status: NEW
Acked-by: Edward O'Callaghan
On 11/05/2016 03:35 AM, Marek Olšák wrote:
> From: Marek Olšák
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=98518
> ---
> src/gallium/winsys/radeon/drm/radeon_drm_surface.c | 2 +-
> 1 file changed, 1
On 03/11/16 07:34 PM, Marek Olšák wrote:
> If you incorporate Dieter's suggestion to fix FMASK, the series is:
>
> Reviewed-by: Marek Olšák
Thanks, but I prefer keeping the FMASK change separate, I'm leaving that
to you or Dieter. I pushed the series with only Nicolai's
https://bugs.freedesktop.org/show_bug.cgi?id=98279
--- Comment #6 from Jan Ziak <0xe2.0x9a.0...@gmail.com> ---
(In reply to Luke A. Guest from comment #5)
> I have told Dave Airlie about rendering issues on this card via irc before
> radv was mainlined.This https://youtu.be/zj9TCgdRn2c was the
https://bugs.freedesktop.org/show_bug.cgi?id=98588
Jan Ziak <0xe2.0x9a.0...@gmail.com> changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=98588
--- Comment #2 from Jan Ziak <0xe2.0x9a.0...@gmail.com> ---
Created attachment 127755
--> https://bugs.freedesktop.org/attachment.cgi?id=127755=edit
vulkancube
--
You are receiving this mail because:
You are the QA Contact for the bug.
You
https://bugs.freedesktop.org/show_bug.cgi?id=98002
--- Comment #8 from Samuel Iglesias ---
(In reply to Samuel Iglesias from comment #7)
> Created attachment 127757 [details]
> SNB screenshot
>
> This is the SNB's screenshot. I wonder if the problem is actually in Mesa,
>
Am 03.11.2016 um 22:06 schrieb Nicolai Hähnle:
From: Nicolai Hähnle
A latent bug in VDPAU interop was exposed by commit
e5cc84dd43be066c1dd418e32f5ad258e31a150a.
Before that commit, the st_vdpau code created samplers with
first_layer == last_layer == 1 that the
On Fri, Nov 04, 2016 at 11:17:13AM +0200, Pohjolainen, Topi wrote:
> On Fri, Oct 28, 2016 at 02:17:12AM -0700, Jason Ekstrand wrote:
> > Previously, blorp copy operations were CCS-unaware so you had to perform
> > resolves on the source and destination before performing the copy. This
> > commit
https://bugs.freedesktop.org/show_bug.cgi?id=98002
--- Comment #7 from Samuel Iglesias ---
Created attachment 127757
--> https://bugs.freedesktop.org/attachment.cgi?id=127757=edit
SNB screenshot
This is the SNB's screenshot. I wonder if the problem is actually in Mesa,
This series is,
Acked-by: Edward O'Callaghan
On 11/04/2016 02:51 PM, Jason Ekstrand wrote:
> From: Kevin Strasser
>
> In order to support FIFO mode without blocking the application on calls
> to vkQueuePresentKHR it is necessary to enqueue
https://bugs.freedesktop.org/show_bug.cgi?id=98002
Samuel Iglesias changed:
What|Removed |Added
CC|
On Fri, Oct 28, 2016 at 02:17:13AM -0700, Jason Ekstrand wrote:
> This commit extends our support of color compression to surfaces without
> the VK_IMAGE_CREATE_MUTABLE_FORMAT_BIT set. These images will never have
> an image view created with a different format then the one set at image
>
On 11/04/2016 01:48 AM, Kenneth Graunke wrote:
> GL_ARB_ES3_compatibility brings ETC2/EAC formats to desktop GL.
>
> The meaning of the GL compressed format list is pretty vague - it's
> supposed to return formats for "general-purpose usage". (GL 4.2
> deprecates the list because of this.)
Am 04.11.2016 um 10:11 schrieb Nicolai Hähnle:
On 04.11.2016 09:47, Christian König wrote:
Am 03.11.2016 um 22:06 schrieb Nicolai Hähnle:
From: Nicolai Hähnle
A latent bug in VDPAU interop was exposed by commit
e5cc84dd43be066c1dd418e32f5ad258e31a150a.
Before that
On Thu, Nov 03, 2016 at 09:07:55PM -0700, Jason Ekstrand wrote:
>On Thu, Nov 3, 2016 at 3:00 PM, Chris Wilson <[1]ch...@chris-wilson.co.uk>
>wrote:
>
> As it stands today, using NO_RELOC without PINNED, the kernel will
> arbitrarily assign an address to each buffer. (The kernel
https://bugs.freedesktop.org/show_bug.cgi?id=98279
--- Comment #7 from Jan Ziak <0xe2.0x9a.0...@gmail.com> ---
(In reply to Jan Ziak from comment #0)
> Also, vulkancube and vulkantri fail to render correctly on this GPU but
> because Dota 2 is a more complex test case there is, in my opinion, no
Good spot,
Reviewed-by: Edward O'Callaghan
On 11/03/2016 09:03 PM, Nicolai Hähnle wrote:
> From: Nicolai Hähnle
>
> From the manpage of asprintf:
>
>"If memory allocation wasn't possible, or some other error occurs,
> these
https://bugs.freedesktop.org/show_bug.cgi?id=98588
Bug ID: 98588
Summary: [vulkan/radeon] vulkancube & vulkansmoketest rendering
issue on R9-390
Product: Mesa
Version: git
Hardware: Other
OS: All
https://bugs.freedesktop.org/show_bug.cgi?id=98588
--- Comment #3 from Jan Ziak <0xe2.0x9a.0...@gmail.com> ---
This bug formalizes a comment in bug 98279.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the
On Fri, Oct 28, 2016 at 02:17:12AM -0700, Jason Ekstrand wrote:
> Previously, blorp copy operations were CCS-unaware so you had to perform
> resolves on the source and destination before performing the copy. This
> commit makes blorp_copy capable of handling CCS-compressed images without
> any
Please add bug tag:
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=97420
On 10/26/2016 02:42 PM, Juan A. Suarez Romero wrote:
Ignore source file, line number and column in glcpp_error() and
glcpp_warning() if those are not available.
It fixes 4 piglit tests:
Reviewed-by: Iago Toral Quiroga
On Thu, 2016-11-03 at 15:31 -0700, Jordan Justen wrote:
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=97447
> Cc: Evan Odabashian
> Signed-off-by: Jordan Justen
> ---
>
this avoids an extra copy which occurs in case of dri2
v1.1: fallback to dri2 if dri3 fails to initialize
Suggested-by: Christian König
Signed-off-by: Nayan Deshmukh
---
src/gallium/state_trackers/vdpau/presentation.c | 58
dri3 allows us to send handle of a texture directly to X
so this patch allows a state tracker to directly send its
texture to X to be used as back buffer and avoids extra
copying
v2: use clip width/height to display a portion of the surface
Suggested-by: Leo Liu
Signed-off-by:
Hi all,
This is re-send of the previous series. It contains the updated patches
in response to Leo, Christian and Emil's comments.
Please Review.
Regards,
Nayan
Nayan Deshmukh (3):
vl/dri3: use external texture as back buffers(v2)
st/vdpau: use dri3 to direclty send the buffer to X(v1.1)
the hack was introduced to avoid an extra copying
but now with dri3 we don't need it anymore
v1.1: rebasing
Signed-off-by: Nayan Deshmukh
---
src/gallium/state_trackers/vdpau/bitmap.c| 2 -
src/gallium/state_trackers/vdpau/device.c| 50 -
https://bugs.freedesktop.org/show_bug.cgi?id=98002
--- Comment #9 from almos ---
I might be able to test this on the proprietary AMD driver, but I can't
download the trace. I click on download, and nothing happens.
--
You are receiving this mail because:
You are the QA
On Friday, 2016-11-04 13:22:07 +0100, Juan A. Suarez Romero wrote:
> Shader can define #version as an integer, including 0.
>
> Initializes version to -1 to know later if shader has defined a #version
> or not.
>
> It fixes 4 piglit tests:
> spec/glsl-1.10/compiler/version-0.frag: crash pass
>
On 31 October 2016 at 15:12, Marek Olšák wrote:
> First, DRI_PRIME should work OK on radeon & amdgpu. I've been testing
> it with 2 GPUs in 2 PCIe slots. (only OpenGL though)
>
> I think the thread got derailed at the beginning and nobody asked the
> important question:
>
> Does
On Fri, Nov 4, 2016 at 8:28 AM, Nicolai Hähnle wrote:
> From: Nicolai Hähnle
>
> A (latent) bug in VDPAU interop was exposed by commit
> e5cc84dd43be066c1dd418e32f5ad258e31a150a.
>
> Before that commit, the st_vdpau code created samplers with
>
On Fri, 2016-11-04 at 14:09 +, Eric Engestrom wrote:
> On Friday, 2016-11-04 13:22:07 +0100, Juan A. Suarez Romero wrote:
> >
> > Shader can define #version as an integer, including 0.
> >
> > Initializes version to -1 to know later if shader has defined a
> > #version
> > or not.
> >
> >
On Thursday, 2016-11-03 15:25:22 +0100, Christian Gmeiner wrote:
> This makes it possible to 'use' the imx-drm driver. Remeber that it
> is not possible to have sysmbol names in C/C++ with a '-' in it.
>
> Signed-off-by: Christian Gmeiner
> ---
>
On 04.11.2016 09:47, Christian König wrote:
Am 03.11.2016 um 22:06 schrieb Nicolai Hähnle:
From: Nicolai Hähnle
A latent bug in VDPAU interop was exposed by commit
e5cc84dd43be066c1dd418e32f5ad258e31a150a.
Before that commit, the st_vdpau code created samplers with
On Thu, 2016-11-03 at 12:23 -0700, Ian Romanick wrote:
> I'm also a little curious how we get to this point with locp being
> NULL.
> Some commentary about that should at least go in the commit message.
So here is the reason.
Mesa initializes parser->version as 0. When finalizes parsing the
Shader can define #version as an integer, including 0.
Initializes version to -1 to know later if shader has defined a #version
or not.
It fixes 4 piglit tests:
spec/glsl-1.10/compiler/version-0.frag: crash pass
spec/glsl-1.10/compiler/version-0.vert: crash pass
Am 04.11.2016 um 13:28 schrieb Nicolai Hähnle:
From: Nicolai Hähnle
A (latent) bug in VDPAU interop was exposed by commit
e5cc84dd43be066c1dd418e32f5ad258e31a150a.
Before that commit, the st_vdpau code created samplers with
first_layer == last_layer == 1 that the
On Fri, Nov 4, 2016 at 11:47 AM, Christian König
wrote:
> Am 04.11.2016 um 10:11 schrieb Nicolai Hähnle:
>>
>> On 04.11.2016 09:47, Christian König wrote:
>>>
>>> Am 03.11.2016 um 22:06 schrieb Nicolai Hähnle:
From: Nicolai Hähnle
Reviewed-by: Marek Olšák
Marek
On Thu, Nov 3, 2016 at 11:16 AM, Nicolai Hähnle wrote:
> From: Nicolai Hähnle
>
> The hardware always treats the alpha channel as unsigned, so add a shader
> workaround. This is rare enough that
On Thu, Nov 3, 2016 at 8:47 PM, Francisco Jerez wrote:
> Ian Romanick writes:
>
>> On 10/28/2016 04:13 PM, Marek Olšák wrote:
>>> From: Marek Olšák
>>>
>>> ---
>>> src/compiler/glsl/ir_optimization.h | 3 ++-
>>>
Until now were validating in/out blocks by listing the inputs in the
consumer stage and then, for each output of the producer, we checked that
it was a match if it was consumed. This method does not catch the case
where the consumer has an input that is not present as an output in the
producer
https://bugs.freedesktop.org/show_bug.cgi?id=98245
Iago Toral changed:
What|Removed |Added
CC||ito...@igalia.com
---
From: Nicolai Hähnle
A (latent) bug in VDPAU interop was exposed by commit
e5cc84dd43be066c1dd418e32f5ad258e31a150a.
Before that commit, the st_vdpau code created samplers with
first_layer == last_layer == 1 that the general texture handling code
would immediately
On Nov 4, 2016 3:29 PM, "Emil Velikov" wrote:
>
> On 31 October 2016 at 15:12, Marek Olšák wrote:
> > First, DRI_PRIME should work OK on radeon & amdgpu. I've been testing
> > it with 2 GPUs in 2 PCIe slots. (only OpenGL though)
> >
> > I think the
The heuristic expecting the entrypoint to be named 'main' was causing
false warnings for modules with only a single shader that happen to use
another name. We now count entrypoints before triggering this warning.
Signed-off-by: Robert Bragg
---
for reference the bug I've created for this:
https://bugs.freedesktop.org/show_bug.cgi?id=97420
and thanks for fixing this
2016-11-04 13:22 GMT+01:00 Juan A. Suarez Romero :
> Shader can define #version as an integer, including 0.
>
> Initializes version to -1 to know later
On 4 November 2016 at 14:57, Marek Olšák wrote:
> On Nov 4, 2016 3:29 PM, "Emil Velikov" wrote:
>>
>> On 31 October 2016 at 15:12, Marek Olšák wrote:
>> > First, DRI_PRIME should work OK on radeon & amdgpu. I've been testing
>> > it
On 1 November 2016 at 22:05, Rob Clark wrote:
> On Tue, Nov 1, 2016 at 5:42 PM, Mauro Rossi wrote:
>>> Mauro or Chih-Wei should be able to answer this (being do static
>>> wallpapers work in i965?).
>>>
>>> Rob
>>
>> Hi, I've perfomed tests with mesa
On Fri, Nov 4, 2016 at 11:31 AM, Emil Velikov wrote:
> On 1 November 2016 at 22:05, Rob Clark wrote:
>> On Tue, Nov 1, 2016 at 5:42 PM, Mauro Rossi wrote:
Mauro or Chih-Wei should be able to answer this (being do static
On Thursday, 2016-11-03 20:51:59 -0700, Jason Ekstrand wrote:
> From: Kevin Strasser
>
> In order to support FIFO mode without blocking the application on calls
> to vkQueuePresentKHR it is necessary to enqueue the request and defer
> calling the server until the next
Jason Ekstrand writes:
> Reviewed-by: Jason Ekstrand
>
> Maybe CC stable?
Already pushed. rzalloc changes didn't look like they were in mesa 13,
so stable is fine.
signature.asc
Description: PGP signature
https://bugs.freedesktop.org/show_bug.cgi?id=97422
Juan A. Suarez changed:
What|Removed |Added
CC|
On Fri, 2016-11-04 at 16:57 +0100, Karol Herbst wrote:
> for reference the bug I've created for this:
> https://bugs.freedesktop.org/show_bug.cgi?id=97420
>
>
I'll tag the commit with this bug.
J.A.
___
mesa-dev mailing list
Hi Nayan,
With this patch, the resizing corruption is fixed, thanks for that.
Still a few comments below.
On 11/04/2016 03:08 AM, Nayan Deshmukh wrote:
dri3 allows us to send handle of a texture directly to X
so this patch allows a state tracker to directly send its
texture to X to be used
On Fri, Nov 4, 2016 at 10:57 AM, Marek Olšák wrote:
> On Nov 4, 2016 3:29 PM, "Emil Velikov" wrote:
>>
>> On 31 October 2016 at 15:12, Marek Olšák wrote:
>> > First, DRI_PRIME should work OK on radeon & amdgpu. I've been testing
>> >
From: Marek Olšák
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=98518
---
src/gallium/winsys/radeon/drm/radeon_drm_surface.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gallium/winsys/radeon/drm/radeon_drm_surface.c
On Thursday, 2016-11-03 20:51:59 -0700, Jason Ekstrand wrote:
> From: Kevin Strasser
>
> In order to support FIFO mode without blocking the application on calls
> to vkQueuePresentKHR it is necessary to enqueue the request and defer
> calling the server until the next
On Fri, Nov 4, 2016 at 12:43 PM, Marek Olšák wrote:
> On Fri, Nov 4, 2016 at 5:23 PM, Alex Deucher wrote:
>> On Fri, Nov 4, 2016 at 10:57 AM, Marek Olšák wrote:
>>> On Nov 4, 2016 3:29 PM, "Emil Velikov"
On Fri, Nov 4, 2016 at 5:23 PM, Alex Deucher wrote:
> On Fri, Nov 4, 2016 at 10:57 AM, Marek Olšák wrote:
>> On Nov 4, 2016 3:29 PM, "Emil Velikov" wrote:
>>>
>>> On 31 October 2016 at 15:12, Marek Olšák
I'm pretty sure we can actually just delete the finishme. There are CTS
tests that do multiple shaders per module and we pass them.
--Jason
On Fri, Nov 4, 2016 at 8:34 AM, Robert Bragg wrote:
> The heuristic expecting the entrypoint to be named 'main' was causing
> false
https://bugs.freedesktop.org/show_bug.cgi?id=98563
Mark Janes changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=98563
--- Comment #1 from Mark Janes ---
Can you indicate a specific device that we can obtain to reproduce this?
A bisection of mesa will help speed resolution to this issue.
--
You are receiving this mail because:
You are
On Fri, Nov 04, 2016 at 12:20:51PM -0400, Leo Liu wrote:
> Hi Nayan,
>
> With this patch, the resizing corruption is fixed, thanks for that.
>
> Still a few comments below.
>
>
> On 11/04/2016 03:08 AM, Nayan Deshmukh wrote:
> > dri3 allows us to send handle of a texture directly to X
> > so
https://bugs.freedesktop.org/show_bug.cgi?id=98563
--- Comment #2 from Trevor Bramble ---
Mark,
I'm using a Diamond BVU5500H.
http://www.diamondmm.com/bvu5500-video-graphics-adapter.html
I'll ask others in that Arch thread to chime in with theirs if it will help.
I'm
https://bugs.freedesktop.org/show_bug.cgi?id=98563
Mark Janes changed:
What|Removed |Added
CC|
Nitpick: I found the commit message hard to understand until I read the
summary.
On 03/11/16 11:47, Timothy Arceri wrote:
> Since we started releasing GLSL IR after linking the only time we can
> print GLSL IR is during linking. When regenerating variants only NIR
> will be available.
> ---
>
https://bugs.freedesktop.org/show_bug.cgi?id=98563
--- Comment #3 from Emil Velikov ---
The following libdrm commit should fix it. Please apply it locally and let me
know if it works.
commit 677cd97dc4a930af508388713f5016baf664ed18
Author: Rob Herring
On Fri, Nov 4, 2016 at 8:58 AM, Eric Engestrom
wrote:
> On Thursday, 2016-11-03 20:51:59 -0700, Jason Ekstrand wrote:
> > From: Kevin Strasser
> >
> > In order to support FIFO mode without blocking the application on calls
> > to
On Fri, Nov 4, 2016 at 9:55 AM, Strasser, Kevin
wrote:
> On Thursday, 2016-11-03 20:51:59 -0700, Jason Ekstrand wrote:
> > From: Kevin Strasser
> >
> > In order to support FIFO mode without blocking the application on calls
> > to
https://bugs.freedesktop.org/show_bug.cgi?id=98555
Emil Velikov changed:
What|Removed |Added
Assignee|intel-3d-bugs@lists.freedes
This is similar to NVC0 and GK110 emitters where we emit
reduction operations instead of atomic operations when the
destination is not used.
Found after writing some tests which check if performance counters
return the expected value. In that case, gred_count returned 0
on gm107 while at least
Reviewed-by: Ilia Mirkin
On Fri, Nov 4, 2016 at 3:08 PM, Samuel Pitoiset
wrote:
> This is similar to NVC0 and GK110 emitters where we emit
> reduction operations instead of atomic operations when the
> destination is not used.
>
> Found after
Are reduction doable on shared atomics as well?
Pierre
On 08:08 pm - Nov 04 2016, Samuel Pitoiset wrote:
> This is similar to NVC0 and GK110 emitters where we emit
> reduction operations instead of atomic operations when the
> destination is not used.
>
> Found after writing some tests which
On 11/04/2016 01:24 PM, Nayan Deshmukh wrote:
On Fri, Nov 04, 2016 at 12:20:51PM -0400, Leo Liu wrote:
Hi Nayan,
With this patch, the resizing corruption is fixed, thanks for that.
Still a few comments below.
On 11/04/2016 03:08 AM, Nayan Deshmukh wrote:
dri3 allows us to send handle of
On 11/04/2016 07:21 PM, Pierre Moreau wrote:
Are reduction doable on shared atomics as well?
AFAIK, no.
Pierre
On 08:08 pm - Nov 04 2016, Samuel Pitoiset wrote:
This is similar to NVC0 and GK110 emitters where we emit
reduction operations instead of atomic operations when the
86 matches
Mail list logo