- 11 Jan, 2019 10 commits
-
-
Linking against LLVM built with BUILD_SHARED_LIBS fails otherwise, as the component is required for the draw module. Reviewed-by:
Dylan Baker <dylan@pnwbakers.com> (cherry picked from commit 4275cae9)
-
Nouveau requires rtti. Often LLVM is configured without rtti, and code with and without cannot be linked safely. Lets just error out if nouveau is requested and llvm is built without rtti. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109202 Fixes: c5a97d65 ("meson: fix builds against LLVM built without rtti") Reviewed-by:
Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl> (cherry picked from commit a2596450)
-
Otherwise there will be symbol collisions for the vector name. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108943 Distro Bug: https://bugs.gentoo.org/673622 Fixes: 42ea0631 ("meson: build clover") Acked-by:
Matt Turner <mattst88@gmail.com> (cherry picked from commit 133a5b83)
-
The gallium drivers do not require a DRI loader. Drop the artificial and unnecessary restriction. Fixes: af9d2761 ("meson: build libmesa_gallium") Signed-off-by:
Emil Velikov <emil.velikov@collabora.com> Reviewed-by:
Dylan Baker <dylan@pnwbakers.com> (cherry picked from commit 9d105818)
-
Fixes: 5e71efef ("meson: Add lmsensors support") Signed-off-by:
Vinson Lee <vlee@freedesktop.org> Reviewed-by:
Dylan Baker <dylan@pnwbakers.com> (cherry picked from commit 0f7ba575)
-
Fixes: 6b4c7047 ("meson: build gallium nine state_tracker") Signed-off-by:
Vinson Lee <vlee@freedesktop.org> Reviewed-by:
Emil Velikov <emil.velikov@collabora.com> (cherry picked from commit 84f39e59)
-
GNU Hurd needs to turn off glx-direct, rather than special case it, we'll just add a toggle. CC: 18.3 <mesa-stable@lists.freedesktop.org> Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com> (cherry picked from commit 7a908869)
-
CC: 18.3 <mesa-stable@lists.freedesktop.org> Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com> (cherry picked from commit 8c77f4c7)
-
Old versions of meson returned ppc64le as the cpu_family for little endian power8 cpus, versions >=0.48 don't do this, so the check wouldn't work in that case. This generalizes the check to work for both old and new versions of meson. Fixes: 34bbb24c ("meson: Add support for ppc assembly/optimizations") Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com> (cherry picked from commit e430a034)
-
Currently we have the three dri "platforms" - drm, apple and windows. Since xf86vidmode is a thing only for the drm one, adjust the preprocessor guards and correctly check for the dependency. v2: terminate the GLX_USE_WINDOWSGL hunk Cc: Jon TURNEY <jon.turney@dronecode.org.uk> Fixes: 5bc50936 ("glx: make xf86vidmode mandatory for direct rendering") Signed-off-by:
Emil Velikov <emil.velikov@collabora.com> Reviewed-by:
Dylan Baker <dylan@pnwbakers.com> Acked-by:
Eric Engestrom <eric.engestrom@intel.com> (cherry picked from commit a95ec138) Squashed with commit: glx: Fix compilation with GLX_USE_WINDOWSGL Sadly, the GLX_USE_APPLEGL and GLX_USE_WINDOWSGL cases are not identical (because GLX_USE_WINDOWSGL uses vtables rather than a maze of ifdefs) Include <sys/time.h> again, as functions prototyped by it are used in the GLX_USE_WINDOWSGL path. Make the include guard around the __glxGetMscRate() definition match the one at it's declaration again, as it's referenced from dri_common.c which is built for GLX_USE_WINDOWSGL. Fixes: a95ec138 ("glx: mandate xf86vidmode only for "drm" dri platforms") Signed-off-by:
Jon Turney <jon.turney@dronecode.org.uk> Reviewed-by:
Emil Velikov <emil.velikov@collabora.com> (cherry picked from commit d512b35b)
-
- 20 Nov, 2018 1 commit
-
-
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 <emil.velikov@collabora.com> Acked-by:
Dylan Baker <dylan@pnwbakers.com> Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com> Fixes: a47c525f "meson: build glx" (cherry picked from commit 5bc50936)
-
- 14 Nov, 2018 3 commits
-
-
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 <eric.engestrom@intel.com> Reviewed-by:
Emil Velikov <emil.velikov@collabora.com> Reviewed-by:
Dylan Baker <dylan@pnwbakers.com> (cherry picked from commit 4fa2fb35)
-
There are two problems: 1) the extra underscore in MISSING_64BIT_ATOMICS 2) we should link with libatomic if the previous test decided we needed it Fixes: d1992255 ("meson: Add build Intel "anv" vulkan driver") Reviewed-and-Tested-by:
Matt Turner <mattst88@gmail.com> (cherry picked from commit 4eab98b6)
-
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)
-
- 26 Oct, 2018 1 commit
-
-
Rob Clark authored
In the pursuit of lowering driver overhead, it became clear that some amount of redesign of how libdrm_freedreno constructs the submit ioctl would be needed. In particular, as the gallium driver is starting to make heavier use of CP_SET_DRAW_STATE state groups/objects, the over- head of tracking cmd buffers and relocs becomes too much. And for "streaming" state, which isn't ever reused (like uniform uploads) the overhead of allocating/freeing ringbuffer[1] objects is too high. This redesign makes two main changes: 1) Introduces a fd_submit object for tracking bos and cmds table for the submit ioctl, making ringbuffer objects more light- weight. This was previously done in the ringbuffer. But we have many ringbuffer instances involved in a submit (gmem + draw + potentially 1000's of state-group rbs), and only need a single bos and cmds table. (Reloc table is still per-rb) The submit is also a convenient place for a slab allocator for ringbuffer objects. Other options would have required locking because, while we can guarantee allocations will only happen on a single thread, free's could happen either on the application thread or the flush_queue thread. With the slab allocator in the submit object, any frees that happen on the flush_queue thread happen after we know that the application thread is done with the submit. 2) Introduce a new "softpin" msm_ringbuffer_sp implementation that does not use relocs and only has cmds table entries for IB1 (ie. the cmdstream buffers that kernel needs to CP_INDIRECT_BUFFER to from the RB). To do this properly will require some updates on the kernel side, so whether you get the softpin or legacy submit/ringbuffer implementation at runtime depends on your kernel version. To make all these changes in libdrm would basically require adding a libdrm_freedreno2, so this is a good point to just pull the libdrm code into mesa. Plus it allows for using mesa's hashtable, slab allocator, etc. And it lets us have asserts enabled for debug mesa buids but omitted for release builds. And it makes life easier if further API changes become necessary. At this point I haven't tried to pull in the kgsl backend. Although I left the level of vfunc indirection which would make it possible to have other backends. (And this was convenient to keep to allow for the "softpin" ringbuffer to coexist.) NOTE: if bisecting a build error takes you here, try a clean build. There are a bunch of ways things can go wrong if you still have libdrm_freedreno cflags. [1] "ringbuffer" is probably a bad name, the only level of cmdstream buffer that is actually a ring is RB managed by kernel. User- space cmdstream is all IB1/IB2 and state-groups. Reviewed-by:
Kristian H. Kristensen <hoegsberg@chromium.org> Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com> Signed-off-by:
Rob Clark <robdclark@gmail.com>
-
- 23 Oct, 2018 1 commit
-
-
VCN jpeg requires new hw ip Signed-off-by:
Boyuan Zhang <boyuan.zhang@amd.com> Reviewed-by:
Leo Liu <leo.liu@amd.com>
-
- 22 Oct, 2018 1 commit
-
-
Dylan Baker authored
r600 doesn't have a hard requirement on LLVM, and therefore doesn't have a hard requirement on libelf. Currently the logic doesn't allow that however. Distro-bug: https://bugs.gentoo.org/669058 Fixes: 5060c51b ("meson: build r600 driver") Reviewed-by:
Matt Turner <mattst88@gmail.com>
-
- 19 Oct, 2018 1 commit
-
-
Kenneth Graunke authored
This warning detects non-void functions with a missing return statement, return statements with a value in void functions, and functions with an bogus return type that ends up defaulting to int. It's already enabled by default with -Wall. Generally, these are fairly serious bugs in the code, which developers would like to notice and fix immediately. This patch promotes it from a warning to an error, to help developers catch such mistakes early. I would not expect this warning to change much based on the compiler version, so hopefully it won't become a problem for packagers/builders. See the GCC documentation or 'man gcc' for more details: https://gcc.gnu.org/onlinedocs/gcc-7.3.0/gcc/Warning-Options.html#index-Wreturn-type Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com>
-
- 17 Oct, 2018 1 commit
-
-
Rob Clark authored
Add helper to add state-groups to emit, and code to emit CP_DRAW_STATE packet if we have any state-groups. Signed-off-by:
Rob Clark <robdclark@gmail.com>
-
- 10 Oct, 2018 1 commit
-
-
Dylan Baker authored
Currently mesa only supports EGL on Unix like systems, cygwin, and haiku. Meson should actually enforce this. This fixes the default build on MacOS. v2: - invert the condition, mark darwin and windows as not supported instead of trying to mark what is supported. v3: - add missing ) v3: - Update comment to reflect condition change in v2 CC: 18.2 <mesa-stable@lists.freedesktop.org> Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com>
-
- 03 Oct, 2018 1 commit
-
-
Seeming copy/paste mistake from configure.ac which uses $2 for the component and $3 for the fancy name printing. Cc: Dylan Baker <dylan@pnwbakers.com> Signed-off-by:
Emil Velikov <emil.velikov@collabora.com> Reviewed-by:
Dylan Baker <dylan@pnwbakers.com>
-
- 25 Sep, 2018 2 commits
-
-
Eric Engestrom authored
That warning fires every time a string function takes an argument that could possibly be longer than its max output, which triggers all over the place, especially when working with file paths ("what if every file path is MAX_PATH long?" is what GCC is saying, which is really annoying when we *know* that "/dev/dri/cardN" is not gonna be 4096 char long and it's safe to store it in a 32-char array). Anyway, we either add a ton of dead code all over the place to make GCC happy, or we get rid of its spam. I chose the latter. Signed-off-by:
Eric Engestrom <eric.engestrom@intel.com> Reviewed-by:
Emil Velikov <emil.l.velikov@gmail.com>
-
Eric Engestrom authored
Signed-off-by:
Eric Engestrom <eric.engestrom@intel.com> Reviewed-by:
Dylan Baker <dylan@pnwbakers.com>
-
- 24 Sep, 2018 1 commit
-
-
Dylan Baker authored
By adding `_llvm == 'true'` to the required argument we can check the 'auto' and 'true' case in one path. Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com>
-
- 21 Sep, 2018 1 commit
-
-
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:
Eric Engestrom <eric.engestrom@intel.com>
-
- 20 Sep, 2018 1 commit
-
-
Reviewed-by:
Dylan Baker <dylan@pnwbakers.com>
-
- 17 Sep, 2018 1 commit
-
-
Dylan Baker authored
Rather than trying to encode all of the rules in a header, lets just put them in the build system where they belong. This fixes the build on FreeBSD, which does have pthraed_setaffinity_np, but it's in a pthread_np.h, not behind _GNU_SOURCE. FreeBSD also implements cpu_set slightly differently, so additional changes would be required to get it working right there anyway. v2: - fix #define in autotools Fixes: 9f1bbbdb ("util: try to fix the Android and MacOS build") Cc: Emil Velikov <emil.velikov@collabora.com> Reviewed-by:
Marek Olšák <marek.olsak@amd.com> Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com>
-
- 06 Sep, 2018 2 commits
-
-
Eric Engestrom authored
By the time Mesa 18.3 comes out (probably December '18), Meson 0.45 will be 9 months old (March '18), so I think this is reasonable. (btw, the currently-required Meson 0.44.1 was released less than 12 days before 0.45, so we're really not bumping by much.) Currently, the Meson versions in the major distributions are: Arch: ships 0.47.2 CentOS: 7 ships 0.47.1 Debian: stable ships 0.37.1, so it hasn't been usable in a long time. everything more recent ships 0.47.2 Fedora: 28 ships 0.45.1 FreeBSD: ships 0.46.1 (ports) Gentoo: ships 0.46.1 OpenSUSE: 15 ships 0.46 Ubuntu: 18.04 ships 0.45.1 Signed-off-by:
Eric Engestrom <eric.engestrom@intel.com> Reviewed-by:
Dylan Baker <dylan@pnwbakers.com>
-
Eric Engestrom authored
The current minimum meson version supported is 0.44.1, so we have met both the 0.43 and 0.44 requirement to not need these hacks anymore :) Signed-off-by:
Eric Engestrom <eric.engestrom@intel.com> Reviewed-by:
Emil Velikov <emil.velikov@collabora.com> Reviewed-by:
Dylan Baker <dylan@pnwbakers.com>
-
- 05 Sep, 2018 1 commit
-
-
Dylan Baker authored
We require a single version of libdrm for all of our libdrm dependencies (core and driver), but the way this is structured can make the error message less than helpful, as one driver might be the one setting the libdrm requirement, while another might be the one that generates the version failure. This adds a simple message to the output announcing which libdrm module set the version, which might be more helpful. v2: - Use message suggested by Eric Engstrom Fixes: c445b1d5 ("meson: Use the same version for all libdrm checks") Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com>
-
- 27 Aug, 2018 2 commits
-
-
There's no Vulkan support for arm atm. Signed-off-by:
Guido Günther <guido.gunther@puri.sm> Reviewed-by:
Dylan Baker <dylan@pnwbakers.com>
-
V2: Add one missing @0@ Signed-off-by:
Guido Günther <guido.gunther@puri.sm> Reviewed-by:
Dylan Baker <dylan@pnwbakers.com>
-
- 20 Aug, 2018 1 commit
-
-
Juan A. Suárez authored
RADV now requires LLVM 6.0 or greater, and thus we can't build dist tarball because swr requires LLVM 5.0. Let's bump required LLVM to 6.0 in swr too. v2: bump also in meson.build (Eric) Fixes: fd1121e8 ("amd: remove support for LLVM 5.0") Cc: Tim Rowley <timothy.o.rowley@intel.com> Cc: Emil Velikov <emil.velikov@collabora.com> Cc: Dylan Baker <dylan@pnwbakers.com> Cc: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com> Reviewed-by:
Bruce Cherniak <bruce.cherniak@intel.com>
-
- 16 Aug, 2018 3 commits
-
-
This adds a freedreno backend for the a6xx generation GPUs, which at the time of this commit is about 98% GLES2 conformant. Much remains to be done - both performance work and feature work towards more recent GLES versions, but this is a good start. Signed-off-by:
Kristian H. Kristensen <hoegsberg@chromium.org> Signed-off-by:
Rob Clark <robdclark@gmail.com>
-
Dylan Baker authored
This handy helper is nice for OSes that are not linux or BSD like (mac and windows) as it knows how to find python3 in odd places. Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com> Reviewed-by:
Jose Fonseca <jfonseca@vmware.com>
-
Dylan Baker authored
It's what autotools has required for a long time. v3: - Use distutils.version.StrictVersion instead of comparing strings Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com> Reviewed-by:
Jose Fonseca <jfonseca@vmware.com>
-
- 10 Aug, 2018 1 commit
-
-
Now that all the build scripts are compatible with both Python 2 and 3, we can flip the switch and tell Meson to use the latter. Since Meson already depends on Python 3 anyway, this means we don't need two different Python stacks to build Mesa. Signed-off-by:
Mathieu Bridon <bochecha@daitauha.fr> Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com> Reviewed-by:
Dylan Baker <dylan@pnwbakers.com>
-
- 08 Aug, 2018 1 commit
-
-
It has no special requirements, size and build-time is effectively zero. v2: Rebase Signed-off-by:
Emil Velikov <emil.velikov@collabora.com> Acked-by:
Dylan Baker <dylan@pnwbakers.com> Reviewed-by:
Adam Jackson <ajax@redhat.com>
-
- 07 Aug, 2018 2 commits
-
-
With version v1.15 the "code" option was deprecated in favour of "private-code" or "public-code". Before the interface symbol generated was exported (which is a bad idea since it's internal implementation detail) and others may misuse it. That was the case with libva approx. 1 year ago. Since then libva was fixed, so we can finally hide it by using "private-code" Inspired by similar xserver patch by Adam Jackson. Signed-off-by:
Emil Velikov <emil.velikov@collabora.com> Reviewed-by:
Dylan Baker <dylan@pnwbakers.com> Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com>
-
Helps when the native wayland-scanner is located outside of PATH. Inspired by the xserver code ;-) Signed-off-by:
Emil Velikov <emil.velikov@collabora.com> Reviewed-by:
Dylan Baker <dylan@pnwbakers.com> Reviewed-by:
Eric Engestrom <eric.engestrom@intel.com>
-