Hi Yogesh,
On Wed, Jul 12, 2017 at 2:18 AM, Marathe, Yogesh
wrote:
>> -Original Message-
>> From: mesa-dev [mailto:mesa-dev-boun...@lists.freedesktop.org] On Behalf
>> Of Tomasz Figa
>> Sent: Tuesday, July 11, 2017 9:59 PM
>> To: Marathe, Yogesh
On Tue, Jul 11, 2017 at 8:18 PM, Kenneth Graunke
wrote:
> On Tuesday, July 11, 2017 7:09:32 PM PDT Jason Ekstrand wrote:
> > This fixes 32-bit builds of the driver.
> >
> > Fixes: 08413a81b93dc537fb0c34327ad162f07e8c3427
> > Cc: Mark Janes
> > Cc:
On Tuesday, July 11, 2017 7:09:32 PM PDT Jason Ekstrand wrote:
> This fixes 32-bit builds of the driver.
>
> Fixes: 08413a81b93dc537fb0c34327ad162f07e8c3427
> Cc: Mark Janes
> Cc: mesa-sta...@lists.freedesktop.org
> ---
> src/intel/vulkan/anv_batch_chain.c | 15
On Tue, Jul 11, 2017 at 7:09 PM, Jason Ekstrand
wrote:
> This fixes 32-bit builds of the driver.
>
I just updated the commit message to be more descriptive:
This fixes 32-bit builds of the driver. Commit 08413a81b93dc537fb0c3
changed things so that we now put
On 2017-07-11 02:31 PM, Marek Olšák wrote:
On Sat, Jul 1, 2017 at 1:03 AM, Andres Rodriguez wrote:
From: Dave Airlie
Instead of allocating memory to back a texture, use the provided memory
object.
Signed-off-by: Andres Rodriguez
This fixes 32-bit builds of the driver.
Fixes: 08413a81b93dc537fb0c34327ad162f07e8c3427
Cc: Mark Janes
Cc: mesa-sta...@lists.freedesktop.org
---
src/intel/vulkan/anv_batch_chain.c | 15 +--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git
The comments are correct - we get -1 and 0. However by adding 1, we
convert this into 0,1. This mostly works for conditionals, but when
negated, this will yield the wrong result. Instead just negate the
values (as they are backwards -- -1 means back instead of front).
Fixes
On Tue, Jul 11, 2017 at 6:02 PM, Matt Turner wrote:
> On Mon, Jul 10, 2017 at 4:05 PM, Connor Abbott wrote:
>> On Mon, Jul 10, 2017 at 3:50 PM, Matt Turner wrote:
>>> On Mon, Jul 10, 2017 at 1:10 PM, Connor Abbott
If size of client memory copy is too large, don't copy. The draw will
access user-buffer directly and then block. This is faster and more
efficient than queuing many large client draws.
Applications that use large draws from client arrays benefit from this.
VMD is an example.
The threshold for
If size of client memory copy is too large, don't copy. The draw will
access user-buffer directly and then block. This is faster and more
efficient than queuing many large client draws.
Applications that use large draws from client arrays benefit from this.
VMD is an example.
The threshold for
Moved reading of environment config options out of
swr_create_screen_internal, into a separate swr_validate_env_options.
This is to keep from cluttering create_screen.
---
src/gallium/drivers/swr/swr_screen.cpp | 60 +++---
1 file changed, 34 insertions(+), 26
Removed the hard-coded constant in favor of a #define. Also removed
TODO comment, the constant value doesn't need an environment
configurable option.
---
src/gallium/drivers/swr/swr_scratch.cpp | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
On Mon, Jul 10, 2017 at 4:05 PM, Connor Abbott wrote:
> On Mon, Jul 10, 2017 at 3:50 PM, Matt Turner wrote:
>> On Mon, Jul 10, 2017 at 1:10 PM, Connor Abbott wrote:
>>> On Thu, Jul 6, 2017 at 4:48 PM, Matt Turner
Thanks very much for Emil and Tomasz's suggestions.
We can see that the out fence needed in queue buffer is get from batch buffer
flushing.
Now we may flush bath buffer at below places:
1. Create sync ===> flush buffer and get out fence from driver
2.Do glFLush() >flush
On Tue, Jul 11, 2017 at 3:34 PM, Nanley Chery wrote:
> On Mon, Jul 10, 2017 at 04:00:23PM -0700, Jason Ekstrand wrote:
> > On Wed, Jun 28, 2017 at 2:14 PM, Nanley Chery
> wrote:
> >
> > > Image layouts only let us know that an image *may* be
On Tue, Jul 11, 2017 at 4:31 PM, Nanley Chery wrote:
> On Mon, Jul 10, 2017 at 02:36:16PM -0700, Jason Ekstrand wrote:
> > On Wed, Jun 28, 2017 at 2:14 PM, Nanley Chery
> wrote:
> >
> > > For readability, bring the assignment of CCS closer to the
---
src/intel/vulkan/anv_image.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/src/intel/vulkan/anv_image.c b/src/intel/vulkan/anv_image.c
index fe5544e..7c4655d 100644
--- a/src/intel/vulkan/anv_image.c
+++ b/src/intel/vulkan/anv_image.c
@@ -264,12 +264,11 @@
This struct represents a full surface state including the addresses of
the referenced main and auxiliary surfaces (if any). This makes
relocation setup substantially simpler and allows us to move 100% of the
surface state setup logic into anv_image where it belongs. Before, we
were manually
This allows us to avoid some extra zeroing.
---
src/intel/vulkan/anv_image.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/src/intel/vulkan/anv_image.c b/src/intel/vulkan/anv_image.c
index 7c4655d..af50ebd 100644
--- a/src/intel/vulkan/anv_image.c
+++
From the Vulkan 1.0.53 spec VU for vkCreateImageView:
"image must have been created with a usage value containing at least
one of VK_IMAGE_USAGE_SAMPLED_BIT, VK_IMAGE_USAGE_STORAGE_BIT,
VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT,
VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT, or
This gives us a single centralized place where we take an image view and
use it to fill out a surface state.
---
src/intel/vulkan/anv_image.c | 171 +
src/intel/vulkan/anv_private.h | 14 +++
src/intel/vulkan/genX_cmd_buffer.c | 37 +++-
3 files
We were early returning and never created the NULL surface state.
Cc: mesa-sta...@lists.freedesktop.org
---
src/intel/vulkan/genX_cmd_buffer.c | 23 +++
1 file changed, 11 insertions(+), 12 deletions(-)
diff --git a/src/intel/vulkan/genX_cmd_buffer.c
---
src/intel/vulkan/anv_private.h | 7 ---
1 file changed, 7 deletions(-)
diff --git a/src/intel/vulkan/anv_private.h b/src/intel/vulkan/anv_private.h
index 4dce360..3e7f9c7 100644
--- a/src/intel/vulkan/anv_private.h
+++ b/src/intel/vulkan/anv_private.h
@@ -2226,13 +2226,6 @@ void
---
src/intel/vulkan/anv_descriptor_set.c | 5 +---
src/intel/vulkan/anv_image.c | 56 ---
src/intel/vulkan/anv_private.h| 21 ++---
src/intel/vulkan/genX_cmd_buffer.c| 29 --
4 files changed, 58 insertions(+), 53
---
src/intel/isl/isl_surface_state.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/src/intel/isl/isl_surface_state.c
b/src/intel/isl/isl_surface_state.c
index 1620c93..e8bdb65 100644
--- a/src/intel/isl/isl_surface_state.c
+++ b/src/intel/isl/isl_surface_state.c
@@
---
src/intel/blorp/blorp_blit.c | 38 +-
src/intel/isl/isl.c | 35 +++
src/intel/isl/isl.h | 23 +++
3 files changed, 71 insertions(+), 25 deletions(-)
diff --git
Cc: mesa-sta...@lists.freedesktop.org
---
src/intel/vulkan/anv_image.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/src/intel/vulkan/anv_image.c b/src/intel/vulkan/anv_image.c
index c84fc8d..a4cf6f8 100644
--- a/src/intel/vulkan/anv_image.c
+++ b/src/intel/vulkan/anv_image.c
@@ -776,6
I started working on another up-and-coming Vulkan feature today and, as is
frequently the case, found a bunch of bugs along the way. This tiny little
series fixes some bugs, does a few cleanups, and does most of the needed
refactoring for said feature. The last two patches are the important
On Mon, Jul 10, 2017 at 02:36:16PM -0700, Jason Ekstrand wrote:
> On Wed, Jun 28, 2017 at 2:14 PM, Nanley Chery wrote:
>
> > For readability, bring the assignment of CCS closer to the assignment of
> > NONE and MCS.
> >
> > Signed-off-by: Nanley Chery
On Tue, Jul 4, 2017 at 3:05 PM, Samuel Pitoiset
wrote:
> A new pair of user SGPR is needed for loading the bindless
> descriptors from shaders. Because the descriptors are global for
> all stages, there is no need to add separate indices for GFX9.
>
> Signed-off-by:
I'd like to keep these for debugging.
Marek
On Thu, Jul 6, 2017 at 6:43 PM, Samuel Pitoiset
wrote:
> Signed-off-by: Samuel Pitoiset
> ---
> src/gallium/auxiliary/util/u_helpers.c | 50
> --
>
Reviewed-by: Marek Olšák
Marek
On Fri, Jul 7, 2017 at 9:52 AM, Samuel Pitoiset
wrote:
> Trivial.
>
> Signed-off-by: Samuel Pitoiset
> ---
> src/gallium/drivers/ddebug/dd_screen.c | 2 +-
> 1 file changed, 1
On Mon, Jul 10, 2017 at 04:00:23PM -0700, Jason Ekstrand wrote:
> On Wed, Jun 28, 2017 at 2:14 PM, Nanley Chery wrote:
>
> > Image layouts only let us know that an image *may* be fast-cleared. For
> > this reason we can end up with redundant resolves. Testing has shown
> >
On Fri, Jul 7, 2017 at 6:34 AM, Andres Rodriguez wrote:
> v2: fix an indentation error
>
> Signed-off-by: Andres Rodriguez
> ---
> src/gallium/drivers/r600/r600_pipe.c | 2 +-
> src/gallium/drivers/radeonsi/si_pipe.c | 2 +-
> 2 files changed, 2
ac, radeonsi, and gallium patches look OK to me except where I commented.
Marek
On Fri, Jul 7, 2017 at 6:24 AM, Andres Rodriguez wrote:
> This series is an initial step towards the implementation of
> EXT_external_objects. It implements the functionality under
>
On Fri, Jul 7, 2017 at 6:24 AM, Andres Rodriguez wrote:
> v2: respective changes for new gallium interface
>
> Signed-off-by: Andres Rodriguez
> ---
> src/mesa/main/dd.h | 15 +++
> src/mesa/main/get.c | 17
This basic extension allows usage of the __DRI_CTX_FLAG_NO_ERROR flag.
This includes support code for classic Mesa drivers to switch on the
no-error mode if the flag is set.
---
include/GL/internal/dri_interface.h | 19 +++
src/gallium/state_trackers/dri/dri2.c|
This only adds the EGL side, needs to be plumbed into Mesa frontend.
---
src/egl/drivers/dri2/egl_dri2.c | 20 ++--
src/egl/drivers/dri2/egl_dri2.h | 1 +
src/egl/main/eglapi.c | 1 +
src/egl/main/eglcontext.c | 30 ++
Hi,
this series implements support for the EGL_KHR_context_create_no
error extension and the associated plumbing through the different
layers of Mesa - EGL, DRI, Gallium state tracker, Mesa frontend. It
took me a while to figure out how everything is connected together
and still it's somewhat
Add a new context flag and plumb it through the various layers of the
context creation code to set up dispatch tables for the no-error mode.
---
src/gallium/include/state_tracker/st_api.h | 1 +
src/gallium/state_trackers/dri/dri_context.c | 3 +++
src/mesa/state_tracker/st_context.c
Allows applications to be whitelisted.
---
src/gallium/state_trackers/dri/dri_context.c| 3 +++
src/gallium/state_trackers/dri/dri_screen.c | 1 +
src/mesa/drivers/dri/common/dri_util.c | 3 +++
src/mesa/drivers/dri/common/xmlpool/t_options.h | 5 +
4 files changed, 12
On Fri, Jul 7, 2017 at 6:24 AM, Andres Rodriguez wrote:
> Signed-off-by: Andres Rodriguez
> ---
> src/gallium/drivers/ddebug/dd_screen.c | 17 +
> src/gallium/include/pipe/p_defines.h | 1 +
> src/gallium/include/pipe/p_screen.h| 13
On Fri, Jul 7, 2017 at 6:24 AM, Andres Rodriguez wrote:
> From: Dave Airlie
>
> Signed-off-by: Andres Rodriguez
> ---
> src/gallium/drivers/radeon/r600_pipe_common.h | 7 ++
> src/gallium/drivers/radeon/r600_texture.c | 112
>
On 07/11/2017 11:15 AM, Charmaine Lee wrote:
Commit a5e733c6b52e93de3000647d075f5ca2f55fcb71 fixes the dangling
framebuffer object by unreferencing the window system draw/read buffers
when context is released. However this can prematurely destroy the
resources associated with these window system
On Fri, Jun 30, 2017 at 12:18 PM, Alex Smith
wrote:
> If a cube image has VK_IMAGE_USAGE_STORAGE_BIT set, the type in an image
> view's descriptor was set to a 2D array (and a few other fields adjusted
> accordingly). This is correct when the image view is actually
Not all objects will be mappable for direct access by the CPU (either
using WC/CPU or WC paths), for example, a dmabuf wrapping an object on a
foreign device or an object wrapping access to stolen memory. Since
either the physical pages are not known or even do not exist, we need to
use the
Looks good. Thanks for the quick fix.
Reviewed-by: Charmaine Lee
From: Brian Paul
Sent: Tuesday, July 11, 2017 2:02 PM
To: mesa-dev@lists.freedesktop.org
Cc: Charmaine Lee; Neha Bhende
Subject: [PATCH] svga:
On Tuesday, July 11, 2017 8:54:25 AM PDT Chris Wilson wrote:
> Valgrind doesn't actually implement VALGRIND_FREELIKE_BLOCK as the
> exact inverse of VALGRIND_MALLOCLIKE_BLOCK. It makes the block
> inaccessible, but still leaves it defined in its allocation tracker i.e.
> it will report the mmap as
Commit bfe1e7737a76e3b046 changed how texture swizzles are set up.
This exposed a latent bug in the VMware driver: we were ignoring
the texture instruction's writemask when applying the 0 and 1
swizzle terms.
This wasn't caught by the Piglit texture swizzle test because it
only exercises fixed
From: Marek Olšák
Add support for 32-bit RGBX/RGBA formats which are required for Android.
The original patch (commit ccdcf91104a5) was reverted (commit
c0c6ca40a25e) in mesa as it broke GLX resulting in swapped colors. Based
on further investigation by Chad Versace, moving
On Sat, Jul 1, 2017 at 1:03 AM, Andres Rodriguez wrote:
> From: Dave Airlie
>
> Instead of allocating memory to back a texture, use the provided memory
> object.
>
> Signed-off-by: Andres Rodriguez
> ---
> src/mesa/main/mtypes.h
On Sat, Jul 1, 2017 at 1:03 AM, Andres Rodriguez wrote:
> From: Dave Airlie
>
> Instead of allocating memory to back a texture, use the provided memory
> object.
>
> Signed-off-by: Andres Rodriguez
> ---
> src/mesa/main/mtypes.h
I'm having some difficulty linking OSdemo32 [Mesa Demo] on MSYS2/MinGW.
Basically, some functions are not included in libGLU.a as the error
returned is undefined reference to __imp_glu... It's strange because these
functions exist in the libGLU source and I am building and using a static
libGLU
Hi all,
I just wanted to send a ping to ask whether there might be a chance to
get this into the next stable release?
I also noted today that this update register merge algorithm fixed The
Witcher 2 for me on r600g (BARTS)
many thanks,
Gert
Am Dienstag, den 04.07.2017, 16:18 +0200 schrieb
Reviewed-by: Bruce Cherniak
> On Jul 11, 2017, at 9:52 AM, Tim Rowley wrote:
>
> From: George Kyriazis
>
> Needed to expose SwrGetInterface
> ---
> src/gallium/drivers/swr/rasterizer/common/os.h | 2 +-
> 1 file
On 11 July 2017 at 16:23, Tomasz Figa wrote:
> Hi Zhongmin,
>
> On Tue, Jul 11, 2017 at 11:02 AM, Wu, Zhongmin wrote:
>> By the way,
>>
>> For cancelBuffer, sorry I forget such function, thanks for notice. It should
>> also pass the same fence fd as
> -Original Message-
> From: mesa-dev [mailto:mesa-dev-boun...@lists.freedesktop.org] On Behalf
> Of Tomasz Figa
> Sent: Tuesday, July 11, 2017 9:59 PM
> To: Marathe, Yogesh
> Cc: Gao, Shuo ; Liu, Zhiquan ;
> Kondapally,
Commit a5e733c6b52e93de3000647d075f5ca2f55fcb71 fixes the dangling
framebuffer object by unreferencing the window system draw/read buffers
when context is released. However this can prematurely destroy the
resources associated with these window system buffers. The problem is
reproducible with
On Tue, Jul 11, 2017 at 9:34 AM, Tomasz Figa wrote:
> On Tue, Jul 11, 2017 at 11:16 PM, Rob Herring wrote:
>> On Tue, Jul 11, 2017 at 8:27 AM, Emil Velikov
>> wrote:
>>> From: Emil Velikov
>>>
>>> As
Hi Yogesh,
On Wed, Jul 12, 2017 at 1:09 AM, Marathe, Yogesh
wrote:
> Hello Figa, Few caveats on that approach
(I'm Tomasz, by the way)
>
>> -Original Message-
>> From: mesa-dev [mailto:mesa-dev-boun...@lists.freedesktop.org] On Behalf
>> Of Tomasz Figa
>>
Hello Figa, Few caveats on that approach
> -Original Message-
> From: mesa-dev [mailto:mesa-dev-boun...@lists.freedesktop.org] On Behalf
> Of Tomasz Figa
> Sent: Tuesday, July 11, 2017 8:58 PM
> To: Wu, Zhongmin
> Cc: Gao, Shuo ; Liu, Zhiquan
Valgrind doesn't actually implement VALGRIND_FREELIKE_BLOCK as the
exact inverse of VALGRIND_MALLOCLIKE_BLOCK. It makes the block
inaccessible, but still leaves it defined in its allocation tracker i.e.
it will report the mmap as lost despite the call to FREELIKE!
Instead of treating the mmap as
-chuanbo.w...@intel.com (bounces)
+"Gao, Shuo" (forgot to add originally, sorry)
On Wed, Jul 12, 2017 at 12:23 AM, Tomasz Figa wrote:
> Hi Zhongmin,
>
> On Tue, Jul 11, 2017 at 11:02 AM, Wu, Zhongmin wrote:
>> By the way,
>>
>> For
Now for real, sorry guys... (Seriously gmail why you do this to me.)
-chuanbo.w...@intel.com (bounces)
+"Gao, Shuo" (forgot to add originally, sorry)
On Wed, Jul 12, 2017 at 12:23 AM, Tomasz Figa wrote:
> Hi Zhongmin,
>
> On Tue, Jul 11, 2017 at 11:02
On Tue, Jul 11, 2017 at 12:05 PM, Grazvydas Ignotas wrote:
> On Tue, Jul 11, 2017 at 12:21 AM, Marek Olšák wrote:
>> From: Marek Olšák
>>
>> Consider the following situation:
>> mtx_lock(mutex);
>> do_something();
>>
Hi Zhongmin,
On Tue, Jul 11, 2017 at 11:02 AM, Wu, Zhongmin wrote:
> By the way,
>
> For cancelBuffer, sorry I forget such function, thanks for notice. It should
> also pass the same fence fd as the queuebuffer.
>
> And Yogesh, you mentioned the gallium, is it another
Well spotted!
Reviewed-by: Lionel Landwerlin
On 11/07/17 16:14, Jason Ekstrand wrote:
Cc: mesa-sta...@lists.freedesktop.org
---
src/intel/vulkan/anv_image.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/src/intel/vulkan/anv_image.c
Cc: mesa-sta...@lists.freedesktop.org
---
src/intel/vulkan/anv_image.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/src/intel/vulkan/anv_image.c b/src/intel/vulkan/anv_image.c
index 76ab923..9992685 100644
--- a/src/intel/vulkan/anv_image.c
+++ b/src/intel/vulkan/anv_image.c
@@ -775,6
On 11 July 2017 at 03:09, Tim Rowley wrote:
> swr used to build and link the rasterizer to the driver, and to support
> multiple architectures we needed to have multiple versions of the
> driver/rasterizer combination, which needed to link in much of mesa.
>
> Changing
https://bugs.freedesktop.org/show_bug.cgi?id=101709
Vedran Miletić changed:
What|Removed |Added
CC||ved...@miletic.net
From: George Kyriazis
Needed to expose SwrGetInterface
---
src/gallium/drivers/swr/rasterizer/common/os.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gallium/drivers/swr/rasterizer/common/os.h
On 11 July 2017 at 15:16, Rob Herring wrote:
> On Tue, Jul 11, 2017 at 8:27 AM, Emil Velikov
> wrote:
>> From: Emil Velikov
>>
>> As said in the EGL_KHR_platform_android extensions
>>
>> For each EGLConfig that belongs
On Tue, Jul 11, 2017 at 11:16 PM, Rob Herring wrote:
> On Tue, Jul 11, 2017 at 8:27 AM, Emil Velikov
> wrote:
>> From: Emil Velikov
>>
>> As said in the EGL_KHR_platform_android extensions
>>
>> For each EGLConfig that
On Tue, Jul 11, 2017 at 8:27 AM, Emil Velikov wrote:
> From: Emil Velikov
>
> As said in the EGL_KHR_platform_android extensions
>
> For each EGLConfig that belongs to the Android platform, the
> EGL_NATIVE_VISUAL_ID attribute is an
On 10 July 2017 at 22:26, Louis-Francis Ratté-Boulianne
wrote:
> Hi,
>
> On Tue, 2017-06-20 at 15:19 +0100, Emil Velikov wrote:
>> > +for (i = 0; i < count; i++) {
>> > + modifiers[i] = (uint64_t) mod_parts[i * 2] << 32;
>> > +
On 11 July 2017 at 14:27, Alex Smith wrote:
> On 10 July 2017 at 05:59, Dave Airlie wrote:
>
>> From: Dave Airlie
>>
>> This patch uses addrlib to workout the tile swizzles according
>> to the surface index. It seems to
From: Emil Velikov
According to the EGL_KHR_platform_gbm extension:
For each EGLConfig that belongs to the GBM platform, the
EGL_NATIVE_VISUAL_ID attribute is a GBM color format, such as
GBM_FORMAT_XRGB.
Which we correctly manage. At the same time
From: Emil Velikov
As said in the EGL_KHR_platform_android extensions
For each EGLConfig that belongs to the Android platform, the
EGL_NATIVE_VISUAL_ID attribute is an Android window format, such as
WINDOW_FORMAT_RGBA_.
Although it should be
On 10 July 2017 at 05:59, Dave Airlie wrote:
> From: Dave Airlie
>
> This patch uses addrlib to workout the tile swizzles according
> to the surface index. It seems to produce the same values as
> amdgpu-pro for the deferred test.
>
> v2: don't apply
Am Dienstag, den 11.07.2017, 15:07 +0200 schrieb Wladimir J. van der
Laan:
> GC3000 has a new LOG instruction, similar to the new SIN and COS instructions.
>
> Generate the new instruction sequence when appropriate; there are
> two occasions, as part of LIT and the generator for the LG2
>
Am 11.07.2017 um 08:25 schrieb Kenneth Graunke:
> Hello,
>
> Mesa master has been hitting assert failures when running "XCOM: Enemy
> Unknown" since commit f8d69beed49c64f883bb8ffb28d4960306baf575, where we
> started asserting that the SAMPLER_STATE LOD Bias value actually fits in
> the correct
GC3000 has a new LOG instruction, similar to the new SIN and COS instructions.
Generate the new instruction sequence when appropriate; there are
two occasions, as part of LIT and the generator for the LG2
instruction itself.
Signed-off-by: Wladimir J. van der Laan
---
On Mon, Jul 10, 2017 at 11:42:18PM +0300, Andres Gomez wrote:
> Ville, has this patch fallen through the cracks ?
Nope. I've still been looking into the issue whenever I've had a
few minutes to spare. I think I have it more or les figured out
at this stage, but I'll need to respin this patch, and
On 10 July 2017 at 22:33, Chad Versace wrote:
> On Mon 10 Jul 2017, Chad Versace wrote:
>> On Fri 07 Jul 2017, Rob Herring wrote:
>> > On Wed, Jul 5, 2017 at 5:14 PM, Chad Versace
>> > wrote:
>> > > On Fri 30 Jun 2017, Rob Herring wrote:
>> >
---
src/mesa/drivers/dri/common/drirc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/mesa/drivers/dri/common/drirc
b/src/mesa/drivers/dri/common/drirc
index 1311db9..be731a0 100644
--- a/src/mesa/drivers/dri/common/drirc
+++ b/src/mesa/drivers/dri/common/drirc
@@ -178,6 +178,9 @@
---
src/mesa/drivers/dri/common/drirc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/mesa/drivers/dri/common/drirc
b/src/mesa/drivers/dri/common/drirc
index 69b735c..1311db9 100644
--- a/src/mesa/drivers/dri/common/drirc
+++ b/src/mesa/drivers/dri/common/drirc
@@ -175,6 +175,9 @@
On Tue, Jul 11, 2017 at 12:21 AM, Marek Olšák wrote:
> From: Marek Olšák
>
> Consider the following situation:
> mtx_lock(mutex);
> do_something();
> util_queue_add_job(...);
> mtx_unlock(mutex);
>
> If the queue is full, util_queue_add_job will
Ping.
On 30 June 2017 at 11:18, Alex Smith wrote:
> If a cube image has VK_IMAGE_USAGE_STORAGE_BIT set, the type in an image
> view's descriptor was set to a 2D array (and a few other fields adjusted
> accordingly). This is correct when the image view is actually
https://bugs.freedesktop.org/show_bug.cgi?id=101334
--- Comment #23 from John ---
Some apps worked, others froze the system.
I'm still hopeful to find a fix here :)
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=101334
--- Comment #22 from Marko ---
(In reply to John from comment #21)
> I believe that's a same generation card, so it would make sense to behave
> similarly.
Yeah. Did it ever work for you? RADV was a no-go on my
When using a read-only CPU mapping, we may encounter stale buffer
contents. For example, the Piglit primitive-restart test offers the
following scenario:
1. Read data via a CPU map.
2. Destroy that buffer.
3. Create a new buffer - obtaining the same one via the BO cache.
4. Call
Just map the buffer and memcpy. This will do a CPU mmap, which should
be reasonably efficient, and doing this gives us full control over the
domains and caching instead of leaving it to the kernel.
This prevents regressions on Braswell in the next commit. Specifically
Hello,
Mesa master has been hitting assert failures when running "XCOM: Enemy
Unknown" since commit f8d69beed49c64f883bb8ffb28d4960306baf575, where we
started asserting that the SAMPLER_STATE LOD Bias value actually fits in
the correct number of bits.
Apparently, XCOM calls
93 matches
Mail list logo