Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
intel-media-driver and intel-gmmlib (formerly named gmmlib)
packages are now on the [community] official repository.
This commit will match the changes that were introduced
in the corresponding repository packages, as follows:
- pkgdesc: includes igpu target specification.
- depends: update gmmlib-git package name to reflect the new one
(intel-gmmlib-git).
- Do not install the profile.d file. It means that the package do
not to offer anymore a way to select the iHD driver. User needs
to read the Arch Wiki and do their homework to select the iHD
driver (Wiki page: currently at 'Hardware video acceleration').
Note:
I have still kept the 'YYYY.x.x' pkgver format instead of adopting
the new 'YY.x.x' one that is being currently used by upstream (and
was adopted by the repository package). Upstream have made a mess
with the versioning schema/method, altering it at each new major
release. So I will be still waiting for '19.x.x' to see if they
will keep it or change it again. Maybe I don't even change it at
all in the future (this will not interfere with the corresponding
repository package anyway). This also removes the need of adding
an epoch number at this moment.
Other changes in this commit:
- pkgver(): cosmetic changes and better handling of year/major.
|
|
Upstream has now enabled again the use of gmmlib installed on
system since September 6, 2018. I hope this is now definitive.
Upstream was having a hard time on this gmmlib dependency due
to internal regressions.
References
----------
https://github.com/intel/media-driver/commit/63dd4ae121542e281ffd76a943b8ece1f18acbb5
https://github.com/intel/media-driver/issues/299#issuecomment-418156001
|
|
Ustream was previously requiring gmmlib source (and providing
gmmlib in package) in order to build, then it switched to require
gmmlib installed on system and then it switched back to require
gmmlib sources due to regressions.
In the future, upstream intends to switch to require gmmlib
installed on system as the final solution, so be prepared for
another change(s) in this approach some upstream commits ahead.
That's the cost that you pay for using a development (-git)
package ;)
References
----------
https://github.com/intel/media-driver/issues/299#issuecomment-418156001
|
|
Upstream intel-media-driver now uses dynamic gmmlib instead of
building it in-source. It also does not install the gmmlib files
anymore. As a result, this package now depends on gmmlib-git.
cmake command was also simplified by upstream.
References
----------
https://github.com/intel/media-driver/pull/270
https://github.com/intel/media-driver/commit/87fadbe90c0bbba64bdf47ed8640ed023858b300
https://github.com/intel/media-driver/commit/54ca9bed5eb383dc89a253fb1a49313cc04b048f
|
|
|
|
|
|
Upstream now provides libgmm_umd.a, which is provided by
gmmlib-git.
|
|
|
|
Upstream currently uses code that is present only on libva git
master. It currently fails to compile with libva 2.1 stable.
|
|
|
|
This will let the user choose which libva driver to use. No other
libva driver package on the official repositories force the setting
of the installed driver by default. This makes sense because the
user can install this additional iHD driver without modifying any
settings that he might have previously configured.
Configuration is done by setting the 'LIBVA_DRIVER_NAME'
environment variable. In the case of this package, it
must be setted to 'iHD'. See the Wiki page on Hardware
video acceleration (VA-API sections) for details. An
informative message is shown during install and upgrade.
|
|
It does not build/work on 32-bit systems. Needs a 64-bit system.
|
|
It was not possible to compile with the default Arch Linux
flags defined in /etc/makepkg.conf due to an upstream issue.
(it was not working with -fno-plt flag). Now it is fixed by
upstream.
References
----------
https://aur.archlinux.org/cgit/aur.git/commit/?h=intel-media-driver-git&id=baeb1117047ba3680f28171e88474a7c9ba5acb4
https://github.com/intel/media-driver/issues/127
https://github.com/intel/media-driver/commit/d95d8f7ab7ac94a2e0f4ee6a4b4794898dc2d3b7
|
|
We can use the cmake command line option MEDIA_BUILD_FATAL_WARNINGS
for this, which is defined in CMakeLists.txt. It's much better than
directly modifying the source code (cmake files).
|
|
References
----------
https://github.com/intel/media-driver/issues/127
|
|
The intel-media-driver is based on a specific libva commit that
comes between the 2.0.0 and 2.1.0 releses. Now that libva 2.1.0
was released, we can use the regular libva package from the
official repositories.
Currently it seems to work fine with libva 2.1.0. Since this is
the development (-git) package, maybe it will be needed to switch
back to libva-git in the future if upstream requires libva
development code in future changes. Let's follow on.
|
|
A recent upstream commit treats warnings as errors. This breaks
compilantion with current libva-git code.
Somehow, building with gcc7 was fixed by upstream.
|
|
|
|
|
|
'-DINSTALL_DRIVER_SYSCONF=' is documented here:
https://github.com/intel/media-driver/commit/81796c8a9e44b878e26064c898e0f4730e8220cf
|
|
|
|
|