Mesa (17.1): 36 new commits

Emil Velikov evelikov at kemper.freedesktop.org
Mon May 8 12:06:04 UTC 2017


URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=da13cc7e4bb1f2fcafadcd3a88f9ee983e1649ee
Author: Emil Velikov <emil.velikov at collabora.com>
Date:   Mon May 8 11:40:34 2017 +0100

    Update version to 17.1.0-rc4
    
    Signed-off-by: Emil Velikov <emil.velikov at collabora.com>

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=3db01cd4e7eac377a991c2a5c63adbdf846cb5bf
Author: Dave Airlie <airlied at redhat.com>
Date:   Sat May 6 21:14:11 2017 +0100

    radv: apply the tess+GS hang workaround to Polaris12 as well
    
    As I pointed out for radeonsi, and AMD confirmed, so fix this
    in radv as well.
    
    Cc: "17.1" <mesa-stable at lists.freedesktop.org>
    Reviewed-by: Bas Nieuwenhuizen <bas at basnieuwenhuizen.nl>
    Signed-off-by: Dave Airlie <airlied at redhat.com>
    (cherry picked from commit 2add79a73291e40621081b9a12938ac1931b9e96)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=396f9ae52f9622e564a7c0912277411d4228292f
Author: Fredrik Höglund <fredrik at kde.org>
Date:   Tue May 2 17:09:27 2017 +0200

    radv/meta: fix restoring a push descriptor set
    
    radv_bind_descriptor_set cannot be used to bind a push descriptor set
    since a push descriptor set does not have a buffer list. However,
    there is no need to add the buffers again when restoring a set, so
    this fix is also an optimization.
    
    Cc: "17.1" <mesa-stable at lists.freedesktop.org>
    Signed-off-by: Fredrik Höglund <fredrik at kde.org>
    Reviewed-by: Bas Nieuwenhuizen <bas at basnieuwenhuizen.nl>
    (cherry picked from commit 5ff48581119258214801de24a327bdd6a29e0ccc)
    [Emil Velikov: resolve trivial conflicts]
    Signed-off-by: Emil Velikov <emil.velikov at collabora.com>
    
    Conflicts:
    	src/amd/vulkan/radv_meta.c

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=0eaab97f2196d171f542d3fdab446e3aeb62d3dd
Author: Kenneth Graunke <kenneth at whitecape.org>
Date:   Wed May 3 19:24:32 2017 -0700

    i965: Don't try to unmap NULL program cache BO.
    
    When running shader-db with intel_stub and recent Mesa, context creation
    fails when making a logical hardware context.  In this case, we call
    intelDestroyContext(), which gets here and tries to unmap the cache BO.
    
    But there isn't one - we haven't made it yet.  So we try to unmap a
    NULL pointer, which used to be safe (it did nothing), but crashes
    after commit 7c3b8ed87859bfdfb985d21685115a729f9cd138.
    
    The result is that we crash rather than failing context creation with
    a nice message.  Either way nothing works, but this is more polite.
    
    Cc: "17.1" <mesa-stable at lists.freedesktop.org>
    Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin at intel.com>
    (cherry picked from commit bc074a45180eddf30ea723bbdf89895e2c7684ca)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=b0394dfe2f8df8fbc748a5d181e1511d68e84afc
Author: Kenneth Graunke <kenneth at whitecape.org>
Date:   Fri May 5 09:20:56 2017 -0700

    Revert "mesa: Require mipmap completeness for glCopyImageSubData(), sometimes."
    
    This reverts commit c5bf7cb52942cb7df9f5d73746ffbf3c102d12cc.
    
    This broke rendering in "Total War: WARHAMMER", which uses a single
    level RGBA_UINT32 texture and the default filter modes of GL_LINEAR
    and GL_NEAREST_MIPMAP_LINEAR.  However, the texture max level is 0,
    so it is actually mipmap complete - it's the integer + linear rule
    that causes the error.
    
    I'm working with Khronos to find a real solution.  However it turns
    out, this patch is not correct and breaks real programs, so let's
    revert it for now.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=100690
    Bugzilla: https://cvs.khronos.org/bugzilla/show_bug.cgi?id=16224
    Cc: "17.1" <mesa-stable at lists.freedesktop.org>
    (cherry picked from commit 1456da91c8a14f77dd347981e2bc95e0644e0fd2)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=639481e3406d1a76472387eb483a554342ba4391
Author: Rob Clark <robdclark at gmail.com>
Date:   Sat May 6 14:00:35 2017 -0400

    freedreno/a3xx: fix hang w/ large render targets and small gmem
    
    Possibly other gen's have a similar limit.  Fixes glmark2 -b shadow
    with larger resolutions on devices with small gmem (for example,
    fullscreen 1080p on 8x16/db410c).
    
    Cc: mesa-stable at lists.freedesktop.org
    Signed-off-by: Rob Clark <robdclark at gmail.com>
    (cherry picked from commit 6050d5bf3d8d0043386de35cad4efa77e8be957e)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=ee0254a12fb1cdadcd263ee77b4c25c055100561
Author: Daniel Stone <daniels at collabora.com>
Date:   Wed May 3 09:38:13 2017 +0100

    i965: Set modifier for imported and duplicated images
    
    When a buffer is being created from FD or GEM flink import, the current
    API makes no provision for passing modifier information along with this.
    Set the modifier for such images to DRM_FORMAT_MOD_INVALID.
    
    Also preserve the modifier when duplicating an image, as will be done by
    GBM when importing from a wl_buffer.
    
    This doubly tripped up Wayland, as the images would first have been
    created (as wl_buffers) with a 0 modifier, and then lost what modifier
    they would've had when being duplicated into gbm_bos.
    
    Fixes: d78a36ea624 ("i965/dri: Handle the linear fb modifier")
    Signed-off-by: Daniel Stone <daniels at collabora.com>
    Reviewed-by: Emil Velikov <emil.velikov at collabora.com>
    (cherry picked from commit 8b8af19065a5bfd06fd0d97b891cfff807704935)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=5b7cc779d21571d9d47f89ce3071d3af27c189b6
Author: Daniel Stone <daniels at collabora.com>
Date:   Wed May 3 18:05:10 2017 +0100

    i965: Use helper function for modifier -> tiling
    
    Use a helper function and struct to convert between a modifier and
    tiling mode, so we can use it later for a tiling -> modifier lookup.
    
    Signed-off-by: Daniel Stone <daniels at collabora.com>
    Reviewed-by: Emil Velikov <emil.velikov at collabora.com>
    (cherry picked from commit 467332a0ab2a2328a37ad302dedd81a654e36313)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=ae9a2c1fc48669441318c158af352deab8bdd709
Author: Grazvydas Ignotas <notasas at gmail.com>
Date:   Tue May 2 20:05:07 2017 +0300

    radv: don't leak DRM devices
    
    After successful drmGetDevices2() call, drmFreeDevices() needs to be called.
    
    Fixes: 743315f2 "radv: do not open random render node(s)"
    Signed-off-by: Grazvydas Ignotas <notasas at gmail.com>
    Reviewed-by: Bas Nieuwenhuizen <bas at basnieuwenhuizen.nl>
    (cherry picked from commit 8aab792e92d8f7d20a1e34169e8a714291ba1c6f)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=64b98a1e72e564979590c20c58c610ed529eee2f
Author: Grazvydas Ignotas <notasas at gmail.com>
Date:   Tue May 2 19:41:13 2017 +0300

    radv: fix possible stack corruption
    
    drmGetDevices2 takes count and not size. Probably hasn't caused problems
    yet in practice and was missed as setups with more than 8 DRM devices
    are not very common.
    
    Fixes: 743315f2 "radv: do not open random render node(s)"
    Signed-off-by: Grazvydas Ignotas <notasas at gmail.com>
    Reviewed-by: Bas Nieuwenhuizen <bas at basnieuwenhuizen.nl>
    (cherry picked from commit 898cbb491b3c02697f006d175d5689893bdf929b)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=7bbece985e7a426c4b2a0efd9e10c661aa2dac13
Author: Bas Nieuwenhuizen <bas at basnieuwenhuizen.nl>
Date:   Tue May 2 23:39:29 2017 +0200

    radv: Don't set dynamic state for pipelines with rasterizer dicard.
    
    All of the dynamic states apply to rasterization & fragment processing,
    so we don't need to set them if we don't rasterize.
    
    We don't clear the dirty flags for them though, so we don't miss any
    updates for the next pipeline with rasterization.
    
    Signed-off-by: Bas Nieuwenhuizen <basni at google.com>
    Reviewed-by: Dave Airlie <airlied at redhat.com>
    Fixes: 76603aa90b8 "radv: Drop the default viewport when 0 viewports are given."
    (cherry picked from commit 9e847eedd5e71fa102003326a3e04e485884fe24)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=929ae9581c11428c43249020ad04c3c82fb97898
Author: Marek Olšák <marek.olsak at amd.com>
Date:   Fri May 5 17:05:05 2017 +0200

    radeonsi: apply the tess+GS hang workaround to Polaris12 as well
    
    Cc: 17.1 <mesa-stable at lists.freedesktop.org>
    Reviewed-by: Alex Deucher <alexander.deucher at amd.com>
    Reviewed-by: Nicolai Hähnle <nicolai.haehnle at amd.com>
    (cherry picked from commit ee5908396e4b0d4be64d8bc486d25c2e95b7fd71)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=d4c08bc8c1322582077356d34208735c86c4955e
Author: Dave Airlie <airlied at redhat.com>
Date:   Fri May 5 10:27:33 2017 +1000

    radv: enable POLARIS12 support.
    
    This just adds the chip in the right places.
    
    We don't set the partial_vs_wave workaround, as radeonsi
    doesn't, but have to confirm it's not required.
    
    Reviewed-by: Bas Nieuwenhuizen <bas at basnieuwenhuizen.nl>
    Cc: "17.1" <mesa-stable at lists.freedesktop.org>
    Signed-off-by: Dave Airlie <airlied at redhat.com>
    (cherry picked from commit a096d8d3f7a8c6dffc91b2ac1794fdd215c054d3)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=cd284ce928b5c99050004a46a02ad70fe376d69e
Author: Nicolas Boichat <drinkcat at chromium.org>
Date:   Fri May 5 10:43:50 2017 +0800

    egl/android: Set EGLSurface.Lost to EGL_TRUE/EGL_FALSE
    
    Lost is an EGLBoolean, so we should assign it to EGL_TRUE/EGL_FALSE,
    not true/false.
    
    Fixes: e5eace58684 ("egl/android: Mark surface as lost when dequeueBuffer fails")
    Fixes: 0212db35040 ("egl/android: Cancel any outstanding ANativeBuffer in surface destructor")
    Reviewed-by: Chad Versace <chadversary at chromium.org>
    (cherry picked from commit 63b12b0c77759a0244416cd1406c2bf50e7c01ec)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=e972294b8e99f9b7c9be8e4adee556ca3e09c9dd
Author: Chad Versace <chadversary at chromium.org>
Date:   Thu May 4 17:46:34 2017 -0700

    egl/android: Mark surface as lost when dequeueBuffer fails
    
    This ensures that future calls to eglSwapBuffers and eglMakeCurrent emit
    an error.
    
    This patch is part of a series for fixing
    android.hardware.camera2.cts.RobustnessTest#testAbandonRepeatingRequestSurface
    on Chrome OS x86 devices.
    
    Cc: mesa-stable at lists.freedesktop.org
    Cc: Tomasz Figa <tfiga at chromium.org>
    Cc: Tapani Pälli <tapani.palli at intel.com>
    Reviewed-by: Nicolas Boichat <drinkcat at chromium.org>
    Reviewed-by: Emil Velikov <emil.velikov at collabora.com>
    (cherry picked from commit e5eace586848511f4ceaffaa2d45131c31c45ae0)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=5ef17d68543aee0d9c8f26aaf33f5d330a76b9d5
Author: Chad Versace <chadversary at chromium.org>
Date:   Thu May 4 17:46:33 2017 -0700

    egl/android: Cancel any outstanding ANativeBuffer in surface destructor
    
    That is, call ANativeWindow::cancelBuffer in droid_destroy_surface().
    
    This should prevent application deadlock when the app destroys the
    EGLSurface after EGL has acquired a buffer from SurfaceFlinger
    (ANativeWindow::dequeueBuffer) but before EGL has released it
    (ANativeWindow::enqueueBuffer).
    
    This patch is part of a series for fixing
    android.hardware.camera2.cts.RobustnessTest#testAbandonRepeatingRequestSurface
    on Chrome OS x86 devices.
    
    Cc: mesa-stable at lists.freedesktop.org
    Cc: Tomasz Figa <tfiga at chromium.org>
    Cc: Tapani Pälli <tapani.palli at intel.com>
    Reviewed-by: Nicolas Boichat <drinkcat at chromium.org>
    Reviewed-by: Emil Velikov <emil.velikov at collabora.com>
    (cherry picked from commit 0212db350407e1331ff23f04136684cf2b7396cf)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=1a23aff6b7ab9c14929c7879ccdb8e19fd4d48da
Author: Chad Versace <chadversary at chromium.org>
Date:   Thu May 4 17:46:33 2017 -0700

    egl: Emit error when EGLSurface is lost
    
    Add a new bool, _EGLSurface::Lost, and check it in eglMakeCurrent and
    eglSwapBuffers. The EGL 1.5 spec says that those functions emit errors
    when the native surface is no longer valid.
    
    This patch just updates core EGL. No driver sets _EGLSurface::Lost yet.
    
    I discovered that Mesa failed to detect lost surfaces while debugging an
    Android CTS camera test,
    android.hardware.camera2.cts.RobustnessTest#testAbandonRepeatingRequestSurface.
    This patch doesn't fix the test though, though, because the test expects
    EGL_BAD_SURFACE when the surface becomes lost, and this patch actually
    complies with the EGL spec. If I interpreted the EGL spec correctly,
    EGL_BAD_NATIVE_WINDOW or EGL_BAD_CURRENT_SURFACE is the correct error.
    
    Cc: mesa-stable at lists.freedesktop.org
    Cc: Tomasz Figa <tfiga at chromium.org>
    Cc: Tapani Pälli <tapani.palli at intel.com>
    Reviewed-by: Nicolas Boichat <drinkcat at chromium.org>
    Reviewed-by: Emil Velikov <emil.velikov at collabora.com>
    (cherry picked from commit 23c86c74cc450a23848b85cfe914376caede1cdf)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=9a226fa669bd10502a9305956da2ce85441926bf
Author: Marek Olšák <marek.olsak at amd.com>
Date:   Fri May 5 01:16:57 2017 +0200

    winsys/amdgpu: fix Polaris12 (RX 550) breakage
    
    reported by Greg White.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=100892
    Cc: 17.1 <mesa-stable at lists.freedesktop.org>
    (cherry picked from commit 69e6eab6533ff48f72223cd21ef640242c52598b)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=41dfe1f275d54f54b30b2b9f1ade7399a82e9228
Author: Marek Olšák <marek.olsak at amd.com>
Date:   Fri Apr 28 19:28:06 2017 +0200

    radeonsi/gfx9: make some PA & DB registers match the closed Vulkan driver
    
    Cc: 17.1 <mesa-stable at lists.freedesktop.org>
    Reviewed-by: Nicolai Hähnle <nicolai.haehnle at amd.com>
    (cherry picked from commit 283a1d1e27b5456cfda848a54b9d74be0993e038)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=ba6cb5d97aac10d2beb1fa3718f3ce86cbf2367f
Author: Emil Velikov <emil.velikov at collabora.com>
Date:   Thu Apr 13 17:17:45 2017 +0100

    glx: glX_proto_send.py: use correct compile guard GLX_INDIRECT_RENDERING
    
    The code itself has nothing to do with shared glapi, thus having it
    behind GLX_SHARED_GLAPI is misleading. Use GLX_INDIRECT_RENDERING
    instead.
    
    The latter macro is set at global scope by the Autotools and Scons build
    systems.
    
    Cc: mesa-stable at lists.freedesktop.org
    Signed-off-by: Emil Velikov <emil.velikov at collabora.com>
    Reviewed-by: Nicolai Hähnle <nicolai.haehnle at amd.com>
    (cherry picked from commit 6177d60a374a3d48969fcb062ac1d82465850cb4)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=7e4b3aec9f325be17317c6d6934d7af7420b15b9
Author: Emil Velikov <emil.velikov at collabora.com>
Date:   Thu Apr 13 19:36:56 2017 +0100

    mesa/dri: always link against shared glapi
    
    Analogous to previous commit. Check with the extensive commit
    description and bug report referenced.
    
    Cc: mesa-stable at lists.freedesktop.org
    Signed-off-by: Emil Velikov <emil.velikov at collabora.com>
    Reviewed-by: Nicolai Hähnle <nicolai.haehnle at amd.com>
    (cherry picked from commit 51accecce7755be9b7eb1baadaec7e4b7d1011af)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=124e7b3bc815f4bbfb501e88f32218f11ccb4ac9
Author: Emil Velikov <emil.velikov at collabora.com>
Date:   Thu Apr 13 18:54:03 2017 +0100

    gallium/dri: always link against shared glapi
    
    In the early days of Xorg and Mesa we had multiple providers of the
    GLAPI. All of those were the ones responsible for dlopening the DRI
    module. Hence it was perfectly fine, and actually expected, for the DRI
    modules to have unresolved symbols.
    
    Since then we've moved the API to a separate shared library and no other
    libraries provide the symbols.
    
    Here comes the picky part:
    It's possible that one uses old Xorg (where libglx.so provides the
    GLAPI) and new Mesa (with DRI modules linking against libglapi.so).
    
    That should still work, since the the libglx.so symbols will take
    precedence over the libglapi.so ones.
    
    I've verified this while running 1.14 series Xorg alongside this (and
    next) patch.
    
    It may seem a bit fragile, but that's of reasonably OK since all of the
    affected Xorg versions have been EOL for years.
    
    The final one being the 1.14 series, which saw its final bug fix release
    1.14.7 in June 2014.
    
    To ensure that the binaries do not have unresolved symbols add
    -no-undefined and $(LD_NO_UNDEFINED), just like we do everywhere else
    throughout mesa.
    
    Cc: mesa-stable at lists.freedesktop.org
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=98428
    Signed-off-by: Emil Velikov <emil.velikov at collabora.com>
    Reviewed-by: Nicolai Hähnle <nicolai.haehnle at amd.com>
    (cherry picked from commit 79a26b663acdffc3f21d6e37f3334495aed16ae5)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=5c43c3fc732917e9e68e531e9d41097126cad202
Author: Ben Boeckel <mathstuf at gmail.com>
Date:   Thu Apr 27 16:31:48 2017 -0400

    scons: update for LLVM 4.0
    
    LLVMDemangle, LLVMGlobalISel, and LLVMDebugInfoMSF are new.
    
    Also update the comment to add irreader to the list of components.
    
    CC: <mesa-stable at lists.freedesktop.org>
    Reviewed-by: Chuck Atkins <chuck.atkins at kitware.com>
    Signed-off-by: Ben Boeckel <ben.boeckel at kitware.com>
    Acked-by: Emil Velikov <emil.velikov at collabora.com>
    Reviewed-by: Jose Fonseca <jfonseca at vmware.com>
    (cherry picked from commit 58f51f0754d736e76248e075bd25424ff4b64b46)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=0bd957be11c20f3fb5e5a088af11431d2ef74b91
Author: Adam Jackson <ajax at redhat.com>
Date:   Wed May 3 11:03:34 2017 -0400

    egl/platform/drm: Don't take display ownership until gbm is initialized
    
    If the gbm_create_device() call here actually did fail, any subsequent
    eglTerminate on the display would segfault.
    
    Cc: <mesa-stable at lists.freedesktop.org>
    Reviewed-by: Eric Anholt <eric at anholt.net>
    Reviewed-by: Emil Velikov <emil.velikov at collabora.com>
    Signed-off-by: Adam Jackson <ajax at redhat.com>
    (cherry picked from commit f258815c7d4187fd83f6944943e78206a6cdc4cb)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=4ad2c57c2647ec8bc30b60df41b5d3d66c9e48e1
Author: Samuel Iglesias Gonsálvez <siglesias at igalia.com>
Date:   Wed May 3 08:02:21 2017 +0200

    anv: anv_gem_mmap() returns MAP_FAILED as mapping error
    
    Take it into account when checking if the mapping failed.
    
    v2:
    - Remove map == NULL and its related comment (Emil)
    
    Signed-off-by: Samuel Iglesias Gonsálvez <siglesias at igalia.com>
    Reviewed-by: Emil Velikov <emil.velikov at collabora.com>
    
    Fixes: 6f3e3c715a7 ("vk/allocator: Add a BO pool")
    Fixes: 9919a2d34de ("anv/image: Memset hiz surfaces to 0 when binding memory")
    Cc: "17.0 17.1" <mesa-stable at lists.freedesktop.org>
    (cherry picked from commit b546c9d318731b988aa3d8c4e4735cdbb596cfbf)
    
    Squashed with:
    
    anv: vkBindImageMemory() should return VK_ERROR_OUT_OF_{HOST,DEVICE}_MEMORY on failure
    
    According to the spec we get VK_ERROR_OUT_OF_HOST_MEMORY or
    VK_ERROR_OUT_OF_DEVICE_MEMORY on vkBindImageMemory failure.
    
    Fixes returned value changed by b546c9d.
    
    Fixes: b546c9d ("anv: anv_gem_mmap() returns MAP_FAILED as mapping error")
    Signed-off-by: Samuel Iglesias Gonsálvez <siglesias at igalia.com>
    Cc: "17.0 17.1" <mesa-stable at lists.freedesktop.org>
    Reviewed-by: Emil Velikov <emil.velikov at collabora.com>
    (cherry picked from commit 939b015736d5091faeabde4f5a373e6a1612c5ed)
    
    Squashed with:
    
    anv: fix anv_gem_mmap comment to not mention NULL
    
    The function cannot return NULL, update the comment accordingly.
    
    Fixes: b546c9d ("anv: anv_gem_mmap() returns MAP_FAILED as mapping error")
    Signed-off-by: Emil Velikov <emil.velikov at collabora.com>
    Reviewed-by: Samuel Iglesias Gonsálvez <siglesias at igalia.com>
    (cherry picked from commit 9d2aa6e5067752efbc0acbd728bc0bde49aefb61)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=14bbc51e6d72cf79660e558a3aa3cf2dcf3df529
Author: Marek Olšák <marek.olsak at amd.com>
Date:   Mon May 1 17:34:41 2017 +0200

    radeonsi/gfx9: fix gl_ViewportIndex
    
    v2: remove unnecessary LLVMBuildAnd calls
    
    Cc: 17.1 <mesa-stable at lists.freedesktop.org>
    Reviewed-by: Nicolai Hähnle <nicolai.haehnle at amd.com>
    (cherry picked from commit f466683cb07796fa89f96ef87a6f076218ae6db8)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=caa6baa688fe0c73c72842835db106dd62a2b716
Author: Christian Gmeiner <christian.gmeiner at gmail.com>
Date:   Tue May 2 22:06:53 2017 +0200

    etnaviv: add L8A8_UNORM texture format
    
    No piglit regressions.
    
    CC: <mesa-stable at lists.freedesktop.org>
    Signed-off-by: Christian Gmeiner <christian.gmeiner at gmail.com>
    Reviewed-by: Philipp Zabel <p.zabel at pengutronix.de>
    (cherry picked from commit a8007ed6872ce1e2cce7145585a4dd1cfd1cec62)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=56922e8f33890f6f24d04f3803eff846d7f23c02
Author: Samuel Iglesias Gonsálvez <siglesias at igalia.com>
Date:   Tue Apr 25 12:28:18 2017 +0200

    i965/vec4: don't modify regioning parameters to the sources of DF align1 instructions
    
    The regioning parameters are now properly set by convert_to_hw_regs()
    and we don't need to fix them in the generator. That latter fix
    previously done in the generator was strictly speaking wrong for any
    non-identity regions.
    
    Signed-off-by: Samuel Iglesias Gonsálvez <siglesias at igalia.com>
    Cc: "17.1" <mesa-stable at lists.freedesktop.org>
    Reviewed-by: Francisco Jerez <currojerez at riseup.net>
    (cherry picked from commit f57e234fdd52331d0aa6656a36efdebea9d11e9d)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=6c96e750f149b85fefb4b396c1305d8af5bf5716
Author: Samuel Iglesias Gonsálvez <siglesias at igalia.com>
Date:   Tue Apr 25 12:18:17 2017 +0200

    i965/vec4: fix register width for DF VGRF and UNIFORM
    
    On gen7, the swizzles used in DF align16 instructions works for element
    size of 32 bits, so we can address only 2 consecutive DFs. As we assumed that
    in the rest of the code and prepare the instructions for this (scalarize_df()),
    we need to set it to two again.
    
    However, for DF align1 instructions, a width of 2 is wrong as we are not
    reading the data we want. For example, an uniform would have a region of
    <0, 2, 1> so it would repeat the first 2 DFs, when we wanted to access
    to the first 4.
    
    This patch sets the default one to 4 and then modifies the width of
    align16 instruction's DF sources when we translate the logical swizzle
    to the physical one.
    
    v2:
    - Remove conditional (Curro).
    
    Signed-off-by: Samuel Iglesias Gonsálvez <siglesias at igalia.com>
    Cc: "17.1" <mesa-stable at lists.freedesktop.org>
    Reviewed-by: Francisco Jerez <currojerez at riseup.net>
    (cherry picked from commit aaeb1c99beed39d85c300ebdb8a7bf056ee6717c)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=ca357be5aa2fbedc115c1e411db87d663e37ebb5
Author: Samuel Iglesias Gonsálvez <siglesias at igalia.com>
Date:   Wed Apr 26 10:12:03 2017 +0200

    i965/vec4: fix vertical stride to avoid breaking region parameter rule
    
    From IVB PRM, vol4, part3, "General Restrictions on Regioning
    Parameters":
    
      "If ExecSize = Width and HorzStride ≠ 0, VertStride must
       be set to Width * HorzStride."
    
    In next patch, we are going to modify the region parameter for
    uniforms and vgrf. For uniforms that are the source of
    DF align1 instructions, they will have <0, 4, 1> regioning and
    the execsize for those instructions will be 4, so they will break
    the regioning rule. This will be the same for VGRF sources where
    we use the vstride == 0 exploit.
    
    As we know we are not going to cross the GRF boundary with that
    execsize and parameters (not even with the exploit), we just fix
    the vstride here.
    
    v2:
    - Move is_align1_df() (Curro)
    - Refactor exec_size == width calculation (Curro)
    
    Signed-off-by: Samuel Iglesias Gonsálvez <siglesias at igalia.com>
    Cc: "17.1" <mesa-stable at lists.freedesktop.org>
    Reviewed-by: Francisco Jerez <currojerez at riseup.net>
    (cherry picked from commit 7f728bce811fc283e672e3a07b008bb7b52de35e)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=e702379663c10251382b4fd38ab329a5f0b7be8b
Author: Philipp Zabel <p.zabel at pengutronix.de>
Date:   Fri Apr 28 13:14:20 2017 +0200

    renderonly: use drmIoctl
    
    To restart interrupted system calls, use drmIoctl.
    
    Fixes: 848b49b288f ("gallium: add renderonly library")
    CC: <mesa-stable at lists.freedesktop.org>
    Suggested-by: Emil Velikov <emil.l.velikov at gmail.com>
    Signed-off-by: Philipp Zabel <p.zabel at pengutronix.de>
    Reviewed-by: Eric Engestrom <eric.engestrom at imgtec.com>
    Reviewed-by: Christian Gmeiner <christian.gmeiner at gmail.com>
    (cherry picked from commit b539335e50b355854202c4b1b42aa4ddbe9289fa)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=ff27a478077f54ea7731b41ce6fed09601ad7018
Author: Philipp Zabel <p.zabel at pengutronix.de>
Date:   Thu Apr 27 18:44:02 2017 +0200

    renderonly: drop resources on destroy
    
    The renderonly_scanout holds a reference on its prime pipe resource,
    which should be released when it is destroyed. If it was created by
    renderonly_create_kms_dumb_buffer_for_resource, the dumb BO also has
    to be destroyed.
    
    Fixes: 848b49b288f ("gallium: add renderonly library")
    CC: <mesa-stable at lists.freedesktop.org>
    Signed-off-by: Philipp Zabel <p.zabel at pengutronix.de>
    Reviewed-by: Emil Velikov <emil.l.velikov at gmail.com>
    Reviewed-by: Christian Gmeiner <christian.gmeiner at gmail.com>
    (cherry picked from commit cd8ee259c8e9b1c16b5c3214595b91eb31e7de19)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=63d75fbfe31bc5a0227d2036d24f37d4aa941fa2
Author: Philipp Zabel <p.zabel at pengutronix.de>
Date:   Thu Apr 27 18:44:01 2017 +0200

    renderonly: close transfer prime_fd
    
    prime_fd is only used to transfer the scanout buffer to the GPU inside
    renderonly_create_kms_dumb_buffer_for_resource. It should be closed
    immediately to avoid leaking the DMA-BUF file handle.
    
    Fixes: 848b49b288f ("gallium: add renderonly library")
    CC: <mesa-stable at lists.freedesktop.org>
    Signed-off-by: Philipp Zabel <p.zabel at pengutronix.de>
    Reviewed-by: Emil Velikov <emil.l.velikov at gmail.com>
    Reviewed-by: Christian Gmeiner <christian.gmeiner at gmail.com>
    (cherry picked from commit ab51cd2f26496500d52f6b2847291d884f711bc2)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=cabca7185b3924837a396094ef52f0bfc351f800
Author: Eric Anholt <eric at anholt.net>
Date:   Wed Mar 8 15:20:31 2017 -0800

    nir: Pick just the channels we want for bitmap and drawpixels lowering.
    
    NIR now validates that SSA references use the same number of channels as
    are in the SSA value.
    
    v2: Reword commit message, since the commit didn't land before the
        validation change did.
    
    Fixes: 370d68babcbb ("nir/validate: Validate that bit sizes and components always match")
    Reviewed-by: Jason Ekstrand <jason at jlekstrand.net> (v1)
    Cc: <mesa-stable at lists.freedesktop.org>
    (cherry picked from commit fba6559a1e76a22135b14490fdf5a6f1de1ae272)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=8020ce02fc2dbc5dd8a8674a64d5a344031b1e03
Author: Randy Xu <randy.xu at intel.com>
Date:   Tue Apr 18 14:27:10 2017 +0800

    i965: Solve Android native fence fd double close
    
    The Android native fence in i965 has two fds: _EGLSync::SyncFd and
    brw_fence::sync_fd.
    
    The semantics of __DRI2fenceExtensionRec::create_fence_fd are unclear on
    whether the DRI driver takes ownership of the incoming fd (which is the
    same incoming fd from eglCreateSync).  i965 did take ownership, but all
    other Mesa drivers do not; instead, they dup the incoming fd. As
    a result, _EGLSync::SyncFd and brw_fence::sync_fd were the same fd, and
    both egl_dri2 and i965 believed they owned it. On eglDestroySync, that
    led to a double-close.
    
    Fix the double-close by making brw_dri_create_fence_fd dup the incoming
    fd, just like the other drivers do.
    
    Signed-off-by: Randy Xu <randy.xu at intel.com>
    Test: Run Vulkan and GLES stress test and no crash.
    Fixes: 6403e376511 ("i965/sync: Implement fences based on Linux sync_file")
    Reviewed-by: Emil Velikov <emil.velikov at collabora.com>
    Reviewed-by: Chad Versace <chadversary at chromium.org>
    [chadv: Polish the commit message]
    Cc: mesa-stable at lists.freedesktop.org
    (cherry picked from commit 6f21b5601cc1260eac53f65c8941b3aa66d0f5e9)

URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=7b4b055a24c081d6befe161c7152d2ccf6057caa
Author: Eric Anholt <eric at anholt.net>
Date:   Fri Apr 14 10:41:51 2017 -0700

    vc4: Only build the NEON code on arm32.
    
    NEON is sufficiently different on arm64 that we can't just reuse this
    code.  Disable it on arm64 for now.
    
    v2: Use PIPE_ARCH_ARM instead, as __ARM_ARCH may be 8 for a 32-bit build
        for a v8 CPU.
    
    Signed-off-by: Eric Anholt <eric at anholt.net>
    Cc: <mesa-stable at lists.freedesktop.org>
    (cherry picked from commit d884d1a6540ec0f60768c30df47f0228a37ea61c)




More information about the mesa-commit mailing list