Commits on Source (50)
-
Juan A. Suarez Romero authored
Signed-off-by:Juan A. Suarez Romero <jasuarez@igalia.com>
-
Karol Herbst authored
v2: fix for specialization constants as well Reviewed-by:
Jason Ekstrand <jason@jlekstrand.net> Cc: mesa-stable@lists.freedesktop.org Signed-off-by:
Karol Herbst <kherbst@redhat.com> (cherry picked from commit b4380cb0)
-
Faith Ekstrand authored
It messes up when trying to lower. Cc: mesa-stable@lists.freedesktop.org Reviewed-by:
Samuel Iglesias Gonsálvez <siglesias@igalia.com> (cherry picked from commit 4266932c)
-
Dylan Baker authored
meson does this for you with its warn levels, so we don't need to set it ourselves. Fixes: d1992255 ("meson: Add build Intel "anv" vulkan driver") Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com> (cherry picked from commit 9c2a95b2) [Juan A. Suarez: resolve trivial conflicts] Signed-off-by:
-
Gert Wollny authored
Transform feedback objects may hold a pointer to a shader program, and at least in Gallium, this must be a valid pointer until ctx->Driver.EndTransformFeedback in glEndTransformFeedback has been called - which is conform with the spec that any program that is part of a current rendering state should only be flagged for deletion by glDeleteProgram. This was not handled properly for the transform feedback objects so that a call sequence glUseProgram(x) glBeginTransformFreedback(...) glPauseTransformFeedback(...) glDeleteProgram(x) glEndTransformFeedback(...) would result in a use after free bug. With this patch the transform feedback object also updates the reference count to the used program thereby keeping the program valid as long as the transform feedback objects links to it. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108713 Fixes: 65458769 mesa: add end_transform_feedback() helper Signed-off-by:
Gert Wollny <gert.wollny@collabora.com> Reviewed-by:
Emil Velikov <emil.velikov@collabora.com> (cherry picked from commit caa964b4)
-
Eric Engestrom authored
Fixes: d1992255 "meson: Add build Intel "anv" vulkan driver" Signed-off-by:
Dylan Baker <dylan@pnwbakers.com> (cherry picked from commit 3832db27)
-
Eric Engestrom authored
`inc_wayland_drm` is only used if wayland is built, and it's already added in that case a few lines below. Fixes: a29869e8 "gbm: Don't traverse backwards for includes" Signed-off-by:
-
Eric Engestrom authored
Those empty variables in the !wayland case are useless and running that meson.build with them breaks the build: [287/850] Generating wayland-drm-client-protocol.h with a custom command. FAILED: src/egl/wayland/wayland-drm/wayland-drm-client-protocol.h client-header ../src/egl/wayland/wayland-drm/wayland-drm.xml src/egl/wayland/wayland-drm/wayland-drm-client-protocol.h /bin/sh: client-header: command not found ninja: build stopped: subcommand failed. Fixes: d1992255 "meson: Add build Intel "anv" vulkan driver" Signed-off-by:
-
Eric Engestrom authored
Fixes dEQP-EGL.functional.get_proc_address.extension.egl_android_blob_cache on builds with glvnd enabled. Fixes: 6f5b5709 "egl: add support for EGL_ANDROID_blob_cache" Signed-off-by:
Tapani Pälli <tapani.palli@intel.com> Reviewed-by:
-
Danylo Piliaiev authored
Handle all cases in calculation of layers count for isl_view taking into account texture view and image unit. st_convert_image was taken as a reference. When u->Layered is true the whole level is taken with respect to image view. In other case only one layer is taken. v3: (Józef Kucia and Ilia Mirkin) - Rewrote patch by taking st_convert_image as a reference - Removed now unused get_image_num_layers function - Changed commit message v4: (Jason Ekstrand) - Added assert Fixes: 5a8c8903 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107856 Signed-off-by:Danylo Piliaiev <danylo.piliaiev@globallogic.com> Reviewed-by:
-
Emma Anholt authored
The DRI3 create_with_modifiers paths don't set tmpl.bind to SCANOUT or SHARED, with the theory that given that you've got modifiers, that's all you need. However, we were looking at the tmpl.bind for setting up the KMS handle in the renderonly case, so we'd end up trying to use vc4's handle on the hx8357d fd. Fixes: 84ed8b67 ("vc4: Set shareable BOs as T tiled if possible") (cherry picked from commit cc0bc76a)
-
Rodrigo Vivi authored
One more CFL ID added to spec. Align with kernel commit d0e062ebb3a4 ("drm/i915/cfl: Add a new CFL PCI ID.") Cc: José Roberto de Souza <jose.souza@intel.com> Cc: Anuj Phogat <anuj.phogat@gmail.com> Signed-off-by:Rodrigo Vivi <rodrigo.vivi@intel.com> Reviewed-by:
Lionel Landwerlin <lionel.g.landwerlin@intel.com> (cherry picked from commit 44f1dcf9)
-
Rodrigo Vivi authored
Many new platforms got added to gen_device_name_to_pci_device_id() but the error message inside aubinator didn't reflected those changes. So syncing on the same order to be sure that we are not missing any now. Cc: Anuj Phogat <anuj.phogat@gmail.com> Cc: Matt Turner <mattst88@gmail.com> Cc: Jordan Justen <jordan.l.justen@intel.com> Signed-off-by:
-
Rodrigo Vivi authored
Amber Lake uses the same gen graphics as Kaby Lake, including a id that were previously marked as reserved on Kaby Lake, but that now is moved to AML page. This follows the ids and approach used on kernel's commit e364672477a1 ("drm/i915/aml: Introducing Amber Lake platform") Reported-by:Timo Aaltonen <timo.aaltonen@canonical.com> Cc: José Roberto de Souza <jose.souza@intel.com> Cc: Anuj Phogat <anuj.phogat@gmail.com> Signed-off-by:
-
Rodrigo Vivi authored
Whiskey Lake uses the same gen graphics as Coffe Lake, including some ids that were previously marked as reserved on Coffe Lake, but that now are moved to WHL page. This follows the ids and approach used on kernel's commit b9be78531d27 ("drm/i915/whl: Introducing Whiskey Lake platform") and commit c1c8f6fa731b ("drm/i915: Redefine some Whiskey Lake SKUs") v2: Lionel noticed that GT{1,2,3} on kernel wasn't following spec when looking to number of EUs, so kernel has been updated. Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com> Cc: José Roberto de Souza <jose.souza@intel.com> Cc: Anuj Phogat <anuj.phogat@gmail.com> Signed-off-by: -
Kenneth Graunke authored
See commit c0c46ca461f136a0ae1ed69da6c874e850aeeb53 in the Linux kernel, where José Roberto de Souza added this new PCI ID there. Reviewed-by:
Jordan Justen <jordan.l.justen@intel.com> Reviewed-by:
-
Emil Velikov authored
Currently we force disable the pager via "|cat" where --no-pager exists. Additionally we could use git show instead of git log -n1. Use those for a slightly more understandable code. Cc: mesa-stable@lists.freedesktop.org Reviewed-by:
-
Emil Velikov authored
With later commits we'll fold all the different scripts into one. Add the explicit prefix, so that we know the origin of the nomination v2: - pass the sha as argument to the function - swap $tag = none for an else statment (Juan) - grep -q instead of using a variable (Eric) - print the tag and commit oneline separately (Eric) v3: - drop unused "tag=none" assignment (Juan) - typo nomination Cc: mesa-stable@lists.freedesktop.org Reviewed-by:
-
Emil Velikov authored
As the comment in get-typod-pick-list.sh says, there's little point in having a duplicate file. Add the new pattern + tag to get-pick-list.sh and nuke this file. v2: - pass the sha as argument to the function - grep -q instead of using a variable (Eric) Cc: mesa-stable@lists.freedesktop.org Reviewed-by:
-
Emil Velikov authored
Having a separate script to handle the fixes tag, brings a number of issues, so let's fold it in get-pick-list.sh. v2: - pass the sha as argument to the function - Keep original sed pattern Cc: mesa-stable@lists.freedesktop.org Reviewed-by:
-
Emil Velikov authored
Currently we match on: - any arbitrary length of, - any a-z A-Z and 0-9 characters At the same time, a commit sha consists of lowercase hexadecimal numbers. Any sha shorter than 8 characters is ambiguous - in some cases even 11+ are required. So change the pattern to a-f0-9 and adjust the length to 8-40. As we're here we could use a single grep, instead of the grep/sed combo. Cc: mesa-stable@lists.freedesktop.org Reviewed-by:
-
Emil Velikov authored
Refactor is_fixes_nomination into a is_sha_nomination helper. This way we can reuse it for more than the usual "Fixes:" tag. Cc: mesa-stable@lists.freedesktop.org Reviewed-by:
-
Emil Velikov authored
Every so often, we forget to add the colon after "fixes". Trivially tweak the script to catch it. Cc: mesa-stable@lists.freedesktop.org Reviewed-by:
-
Emil Velikov authored
We have a number of cases were devs will use a tag "broken by". While it's not something officially documented or recommended, checking for it is trivial enough. Cc: mesa-stable@lists.freedesktop.org Reviewed-by:
-
Emil Velikov authored
Latter is rather picky wrt surrounding white space. The explicit `test` doesn't have that problem, plus the statements read a bit easier. Cc: mesa-stable@lists.freedesktop.org Reviewed-by:
-
Emil Velikov authored
Currently we detect when a breaking commit: - has landed in stable, and - is referenced by a untagged fix in master Yet we did not consider the case of breaking commit: - prior to the branchpoint, and - is referenced by a untagged fix in master Addressing the latter is extremely slow, due to the size of the lookup. That said, we can trivially use the existing is_sha_nomination() helper to catch reverts. Cc: mesa-stable@lists.freedesktop.org Reviewed-by:
-
Dylan Baker authored
We already correctly handle va being auto, but we force it to being true, which is bad. Fixes 94cf3970 ("meson: Fix auto option for va") Reviewed-by:
-
Brian Paul authored
This reverts commit a5fd54f8. The whole point was to add a way to pass -DVMX86_STATS to the build, but we can do that with a command line argument when we invoke scons. Reviewed-by:
José Fonseca <jfonseca@vmware.com> (cherry picked from commit d6be0b55)
-
Lionel Landwerlin authored
According to the EGL_EXT_image_dma_buf_import spec, creating an EGL image with a DRM format not supported should yield the BAD_MATCH error : " * If <target> is EGL_LINUX_DMA_BUF_EXT, and the EGL_LINUX_DRM_FOURCC_EXT attribute is set to a format not supported by the EGL, EGL_BAD_MATCH is generated. " Signed-off-by:Chad Versace <chadversary@chromium.org> (cherry picked from commit 1c56d211)
-
Juan A. Suarez Romero authored
extra: intel/aub_viewer is not present in branch Signed-off-by: -
Juan A. Suarez Romero authored
extra: intel/aub_viewer is not present in branch Signed-off-by: -
Emil Velikov authored
The only place where the package is needed is for building the DRI based libGL library. Cc: mesa-stable@lists.freedesktop.org Signed-off-by:
-
Emil Velikov authored
Currently we detect the module and if missing, the glXGetMsc* API is effectively a stub, always returning false. This is what effectively has been happening with our meson build :-( Thus users have no chance of using it - they cannot even distinguish if the failure is due to a misconfigured build. There's no reason for keeping xf86vidmode optional - it has been available in all distributions for years. Cc: mesa-stable@lists.freedesktop.org Signed-off-by:
-
Emil Velikov authored
Required by the x11 WSI Fixes: df82012b ("travis: add meson build for vulkan drivers.") Signed-off-by:
-
Andrii Simiklit authored
There's no point reverting to the last saved point if that save point is the empty batch, we will just repeat ourselves. v2: Merge with new commits, changes was minimized, added the 'fixes' tag v3: Added in to patch series v4: Fixed the regression which was introduced by this patch Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108630 Reported-by:Mark Janes <mark.a.janes@intel.com> The solution provided by: Jordan Justen <jordan.l.justen@intel.com> CC: Chris Wilson <chris@chris-wilson.co.uk> Fixes: 3faf56ff "intel: Add an interface for saving/restoring the batchbuffer state." Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107626 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108630 (fixed in v4) Signed-off-by:
Andrii Simiklit <andrii.simiklit@globallogic.com> Reviewed-by:
Kenneth Graunke <kenneth@whitecape.org> (cherry picked from commit b787dcf5)
-
Gert Wollny authored
This fixes two memory leaks reported by ASAN: Direct leak of 248 byte(s) in 1 object(s) allocated from: in malloc (/usr/lib64/gcc/x86_64-pc-linux-gnu/7.3.0/libasan.so+0xdb880) in r600_alloc_buffer_struct ../../samba/mesa/src/gallium/drivers/r600/r600_buffer_common.c:578 in r600_buffer_create ../../samba/mesa/src/gallium/drivers/r600/r600_buffer_common.c:600 in r600_resource_create_common ../../samba/mesa/src/gallium/drivers/r600/r600_pipe_common.c:1265 in r600_resource_create ../../samba/mesa/src/gallium/drivers/r600/r600_pipe.c:725 in pipe_buffer_create ../../samba/mesa/src/gallium/auxiliary/util/u_inlines.h:291 in update_gs_block_state ../../samba/mesa/src/gallium/drivers/r600/r600_state_common.c:1482 Direct leak of 248 byte(s) in 1 object(s) allocated from: in malloc (/usr/lib64/gcc/x86_64-pc-linux-gnu/7.3.0/libasan.so+0xdb880) in r600_alloc_buffer_struct ../../samba/mesa/src/gallium/drivers/r600/r600_buffer_common.c:578 in r600_buffer_create ../../samba/mesa/src/gallium/drivers/r600/r600_buffer_common.c:600 in r600_resource_create_common ../../samba/mesa/src/gallium/drivers/r600/r600_pipe_common.c:1265 in r600_resource_create ../../samba/mesa/src/gallium/drivers/r600/r600_pipe.c:722 in pipe_buffer_create ../../samba/mesa/src/gallium/auxiliary/util/u_inlines.h:291 in update_gs_block_state ../../samba/mesa/src/gallium/drivers/r600/r600_state_common.c:1489 Signed-off-by:
Roland Scheidegger <sroland@vmware.com> (cherry picked from commit 61b53543)
-
Faith Ekstrand authored
It affects apply_pipeline_layout. Shaders compiled with the wrong value will work but they may not be robust as requested by the app. Cc: mesa-stable@lists.freedesktop.org Reviewed-by:
Iago Toral Quiroga <itoral@igalia.com> (cherry picked from commit 617e402b) [Juan A. Suarez: resolve trivial conflicts] Signed-off-by:
-
Eric Engestrom authored
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108829 Fixes: 3218056e "meson: Build i965 and dri stack" Signed-off-by:
-
Marek Olšák authored
Cc: 18.2 18.3 <mesa-stable@lists.freedesktop.org> Reviewed-by:
Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl> (cherry picked from commit 82aa07f8)
-
Marek Olšák authored
Cc: 18.2 18.3 <mesa-stable@lists.freedesktop.org> Reviewed-by:
-
Bas Nieuwenhuizen authored
We used the layer count which results in an off by one error. Not sure this really affects anything. Fixes: f4e499ec "radv: add initial non-conformant radv vulkan driver" Reviewed-by:
Dave Airlie <airlied@redhat.com> (cherry picked from commit 3c96a1e3)
-
Gert Wollny authored
When a shader program is de-serialized the gl_shader_program passed in may actually still hold memory allocations for the transform feedback varyings. If that is the case, free the varying names and reallocate the new storage for the names array. This fixes a memory leak: Direct leak of 48 byte(s) in 6 object(s) allocated from: in malloc (/usr/lib64/gcc/x86_64-pc-linux-gnu/7.3.0/libasan.so+0xdb880) in transform_feedback_varyings ../../samba/mesa/src/mesa/main/transformfeedback.c:875 in _mesa_TransformFeedbackVaryings ../../samba/mesa/src/mesa/main/transformfeedback.c:985 ... Indirect leak of 42 byte(s) in 6 object(s) allocated from: in __interceptor_strdup (/usr/lib64/gcc/x86_64-pc-linux-gnu/7.3.0/libasan.so+0x761c8) in transform_feedback_varyings ../../samba/mesa/src/mesa/main/transformfeedback.c:887 in _mesa_TransformFeedbackVaryings ../../samba/mesa/src/mesa/main/transformfeedback.c:985 Fixes: ab2643e4 glsl: serialize data from glTransformFeedbackVaryings Signed-off-by:
-
Erik Faye-Lund authored
The explanation quotes the spec on the following wording to justify the error: "An INVALID_VALUE error is generated if xoffset + width is greater than the texture’s width, yoffset + height is greater than the texture’s height, or zoffset + depth is greater than the texture’s depth." However, this shouldn't generate an error in the case where *all three* of width, xoffset and the texture's width are zero. In this case, we end up generating an unspecified error. So let's remove this check, and instead make sure that we consider this as an empty texture. So let's not generate an error, there's non mandated in the spec in xoffset/yoffset/zoffset = 0 case. We already avoid doing any work in this case, because of the final, non-error generating check in this function. Fixes: b37b35a5 "getteximage: assume texture image is empty for non defined levels" Signed-off-by:
Erik Faye-Lund <erik.faye-lund@collabora.com> Reviewed-by:
-
Juan A. Suarez Romero authored
fixes: This commit requires commits 854202f70e6 and 84bc5738401 which did not land in branch. Signed-off-by: -
Juan A. Suarez Romero authored
Signed-off-by: -
Juan A. Suarez Romero authored
Signed-off-by: -
Juan A. Suarez Romero authored
Signed-off-by: -
Timo Aaltonen authored
-
Timo Aaltonen authored
-
Timo Aaltonen authored
bin/get-fixes-pick-list.sh
deleted
100755 → 0
bin/get-typod-pick-list.sh
deleted
100755 → 0
docs/relnotes/18.2.6.html
0 → 100644