When 'opengl' is not set in DISTRO_FEATURES, ${libdir}/pkgconfig is an
empty directory and cause installed-vs-shipped error.
(From OE-Core rev: 9e373fec2013c5b2f9297e8f88317628ba9b7dce)
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Daniel Stone (3):
drm/atomic: Refuse to add invalid objects to requests
headers: Sync with drm-next
headers: Update README
Dylan Baker (1):
meson: don't use compiler.has_header
Emil Velikov (1):
Revert "libdrm: intel/Android.mk: Filter libdrm_intel library requirements on x86/x86_64"
Eric Engestrom (13):
freedreno: add missing symbols to symbol-check
meson: use pkg-config to detect libatomic_ops
meson: make it easy to add headers to check
meson: detect alloca.h
meson,configure: always define HAVE_OPEN_MEMSTREAM
meson,configure: always define HAVE_VISIBILITY
meson,configure: always define UDEV
meson: replace `if(compiles) have=true` with `have=compiles`
meson,configure: include config.h automatically
meson: drop unneeded dependency to libudev
meson: move line to allow using `config` earlier
meson: drop unnecessary variable
xf86drmMode: merge successive mutually-exclusive #ifs
Gowtham Tammana (1):
omap: add Android build support
Inki Dae (1):
tests: fix memory leak issue
James Zhu (1):
tests/amdgpu: add vce mv tests support and sets
John Stultz (3):
libdrm: intel/Android.mk: Filter libdrm_intel library requirements on x86/x86_64
libdrm: Use readdir instead of readdir_r to avoid build warnings
libdrm: gralloc_handle.h: Fix build issue with Android
Marek Olšák (1):
Revert "amdgpu:support 16 ibs per submit for PAL/SRIOV"
Matt Atwood (1):
Intel: Add a Kaby Lake PCI ID
Michel Dänzer (1):
amdgpu: Deinitialize vamgr_high{,_32}
Paulo Zanoni (1):
intel: add support for ICL 11
Qiang Yu (1):
amdgpu:support 16 ibs per submit for PAL/SRIOV
Rex Zhu (1):
headers: sync up amdgpu_drm.h with drm-next
Rob Clark (2):
freedreno: add fd_pipe refcounting
bump version for release
Rodrigo Vivi (1):
intel/intel_chipset.h: Sync Cannonlake IDs.
Sabre Shao (1):
drm/amdgpu: Remove IB count checking
Satyajit (1):
libdrm: amdgpu: Adding DRM_RDWR flag in amdgpu_bo_export
Seung-Woo Kim (1):
tests/exynos: remove dead condition
Stefan Schake (1):
android: Add missing include exports
Tomasz Figa (1):
intel: Do not use libpciaccess on Android
Xiaojie Yuan (1):
amdgpu: enlarge the maximum number of cards supported
(From OE-Core rev: 805c362871b1a03fbee941b628f2e8aca0f4bb51)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These dependencies are in the x11 PACKAGECONFIG and will magically transform for
nativesdk builds.
(From OE-Core rev: 5e55efce4f7ecb3fcb219a15dcbc031f0f233cb1)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Wayland 1.15+ now ships libwayland-egl by itself, so Mesa should remove
its instance. Previous commit 6e5952fcfc13ff4b63c9376bd41a1dbba957f425
only removed .so libraries, but left .la, which resulted in conflict.
(From OE-Core rev: 7a1d0f532bb2a6772e24a9fd4515bd1f3ab15324)
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ensure that python2 is not assumed to be python which can
point to python3 in some cases, when building gallium-llvm
there are scripts which are requiring python2 and wont work
with python3
(From OE-Core rev: c693b7ec8914460c891a5fb8bd36fb9401e62ac0)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
xcalibrate was replaced with other xinput touchscreen protocols,
drop this remaining remnant.
(From OE-Core rev: a1cf2b40b5bf0ead10d3bff155467d4f559e1b73)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The extensions patch was merged upstream and is no longer needed.
(From OE-Core rev: 1e89528b259e784e2e8d526dc2e0357eccddfd1c)
Signed-off-by: Armin Kuster <akuster@mvista.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Xorg upstream have replaced the individual xorg proto repositories with one
master repository. This converts to the new system.
The only one not included is calibrateproto which was depreciated entirely
and replaced be xinput. We can drop this entirely.
(From OE-Core rev: 460a2b27af8d023b27703b491331c8cbe7aad0ff)
Signed-off-by: Armin Kuster <akuster@mvista.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
patch 0001-include-stdint.h-for-SSIZE_MAX-and-SIZE_MAX-definiti.patch remove
as it is included in update
(From OE-Core rev: 486b85ced3d309978558cf01dece4f5c1982013e)
Signed-off-by: Armin Kuster <akuster@mvista.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
drop patches included in update
(From OE-Core rev: f5341f043ed63db717c74677ff831fd5de7ce7ef)
Signed-off-by: Armin Kuster <akuster@mvista.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It appears that sometimes xserver-nodm.service is starting before
display driver finished loading causing the following failure in
Xorg log:
(EE) open /dev/dri/card0: No such file or directory
The introduced by this patch is to restart the service,
hopefully the display driver will finish loading.
(From OE-Core rev: c3935f11f2807ef73f224b6690886d863788310d)
Signed-off-by: Ramon Fried <rfried@codeaurora.org>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Adpat to the upgrade from 5.0 -> 6.0.
(From OE-Core rev: dc52f9cf343df4c2d77bee0e47004466321e7edb)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This version has been published at April 03, 2018, and it is a bugfix
only release.
The release includes several important fixes that were made as part of
18.0.1 development cycle. Full list of bug fixes can be see online at:
https://www.mesa3d.org/relnotes/17.3.8.html
(From OE-Core rev: 782fb864349d4f5c07a38f0e117659bfb841d3c2)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The 'glamor' PACKAGECONFIG in xserver-xorg creates a dependency on libgbm
which can be satisfied in some cases by mesa, in others by blobs such as mali.
(From OE-Core rev: 5f8050722169a931b8e9078b8757216ba7a84506)
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Mesa only PROVIDES these features if they are enabled via PACKAGECONFIG.
Therefore make the PROVIDES conditional depending on whether or not these
features have been enabled.
(From OE-Core rev: 8b1e57eb8c959c0f0a5d9a7e0c2e0811c515ea08)
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
replace_glibc_check_with_linux.patch was accepted upstream with
modifications.
(From OE-Core rev: 94cf27ebc5d3e3fafa85f3bb1ca54f606bb411ad)
Signed-off-by: Maxin B. John <maxin.john@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This version has been published at March 21, 2018, and it is a bugfix
only release. It includes several important fixes that were made as
part of 18.0.0 development cycle.
Full list of bug fixes can be see online at:
https://www.mesa3d.org/relnotes/17.3.7.html
(From OE-Core rev: 3601c079e15f3570b9b90cd8775e4e90175d1bb5)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Debian and Fedora both carry this patch, and the xf86-video-modesetting
driver seems better on recent hardware.
As an example, on a NUC6CAYS, the x11perf -aa10text and -rgb10text tests
see around a 20x increase.
[YOCTO #12019]
[YOCTO #12390]
(From OE-Core rev: 2e4934d5d4b2745ffcd76020b307b9021f8d8853)
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Now that we have recipe-specific-sysroots we don't need to exclude recipes from
world builds because they conflict with other recipes, as they'll all be built
with their own sysroots.
(From OE-Core rev: b2f3ac4d994a1921791f6bd0cdb3591586733694)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
(From OE-Core rev: 77fb72c76c8a5b2229a32f36a913a3293e9d2b56)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
(From OE-Core rev: 0cff8ae54066b25ffbe1efaa3f0a1d84aa89ebe1)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
(From OE-Core rev: 625be3dd6e3069333a3c94ca8f23129b23e4425b)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
(From OE-Core rev: 020ef81aa072c79f427111e5057d29ded849c48c)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
(From OE-Core rev: 385d26b7f0aeb6085bd7d96332b760057bd24537)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
(From OE-Core rev: 320f03b8492e5259c45e7c59b62571d5a827ee59)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a minor release, announced in March 5th, 2018, which includes
following changes:
,----
| Andrey Grodzovsky (1):
| amdgpu: Fix mistake in initial hole size calculation.
|
| Christian König (3):
| amdgpu: mostly revert "use the high VA range if possible v2"
| amdgpu: add AMDGPU_VA_RANGE_HIGH
| amdgpu: fix "add AMDGPU_VA_RANGE_HIGH"
|
| Chunming Zhou (1):
| test/amdgpu: disable bo eviction test by default
|
| Eric Engestrom (1):
| meson: add configuration summary
|
| Heiko Becker (1):
| *-symbol-check: Don't hard-code nm executable
|
| Igor Gnatenko (1):
| meson: do not use cairo/valgrind if disabled
|
| Jonathan Gray (1):
| meson/configure.ac: pthread-stubs not present on OpenBSD
|
| Marek Olšák (2):
| meson: bump the version number
| RELEASING: mention meson
|
| Michel Dänzer (1):
| tests/amdgpu: Fix misspellings of "suite"
|
| Rob Clark (2):
| freedreno: add interface to get buffer address
| bump version for release
|
| Rob Herring (4):
| android: revert making handle magic and version members const
| android: fix mis-named alloc_handle_t
| android: add helper to convert buffer_handle_t to gralloc_handle_t ptr
| android: fix gralloc_handle_create() problems
|
| Thierry Reding (2):
| drm/fourcc: Fix fourcc_mod_code() definition
| drm/tegra: Sanitize format modifiers
`----
(From OE-Core rev: eef14164fb663d722234dbaf98611cf7ff0043d9)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
(From OE-Core rev: 453a433768bff76e4d3ad9bf40fd9d8210b0950e)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Armin Kuster
Kai Kang
Denys Dmytriyenko
Otavio Salvador
Ross Burton
Martin Jansa
Khem Raj
Richard Purdie
Armin Kuster
Ramon Fried
Andreas Müller
Trevor Woerner
Maxin B. John
California Sullivan