From: Marius Bakke <mbakke@fastmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>, 36814@debbugs.gnu.org
Subject: [bug#36814] [PATCH 1/2] gnu: Add intel-vaapi-driver.
Date: Sat, 27 Jul 2019 20:35:38 +0200 [thread overview]
Message-ID: <877e83496t.fsf@devup.no> (raw)
In-Reply-To: <20190726033037.1203-1-me@tobias.gr>
[-- Attachment #1: Type: text/plain, Size: 2394 bytes --]
Tobias Geerinckx-Rice via Guix-patches <guix-patches@gnu.org> writes:
> * gnu/packages/video.scm (intel-vaapi-driver): New public variable.
> ---
> gnu/packages/video.scm | 38 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 38 insertions(+)
>
> diff --git a/gnu/packages/video.scm b/gnu/packages/video.scm
> index 4b9e05edfe..f068c5df65 100644
> --- a/gnu/packages/video.scm
> +++ b/gnu/packages/video.scm
> @@ -2695,6 +2695,44 @@ of modern, widely supported codecs.")
> ;; Combination under GPLv2. See LICENSE.
> (license license:gpl2)))
>
> +(define-public intel-vaapi-driver
> + (package
> + (name "intel-vaapi-driver")
> + (version "2.3.0")
> + (source
> + (origin
> + (method url-fetch)
> + (uri (string-append "https://github.com/intel/intel-vaapi-driver/"
> + "releases/download/" version "/intel-vaapi-driver-"
> + version ".tar.bz2"))
> + (sha256
> + (base32 "1qyzxh3p8cw4fv8bz9zd4kc8hajlaps7xryzh6pad814n3m5sbjw"))))
> + (build-system gnu-build-system)
> + (native-inputs
> + `(("pkg-config" ,pkg-config)))
> + (inputs
> + `(("libdrm" ,libdrm)
> + ("libva" ,libva)
> + ("libx11" ,libx11)))
> + (arguments
> + `(#:phases
> + (modify-phases %standard-phases
> + (add-before 'configure 'set-up-directories
> + (lambda* (#:key outputs #:allow-other-keys)
> + (let ((out (assoc-ref outputs "out")))
> + (setenv "LIBVA_DRIVERS_PATH" (string-append out "/lib/dri"))
> + #t))))))
Can this be passed in #:configure-flags? What does it do, anyway? :-)
> + (home-page "https://01.org/linuxmedia/vaapi")
> + (synopsis "VA-API video acceleration driver for Intel GEN Graphics devices")
> + (description
> + "This is the @acronym{VA-API, Video Acceleration API} back end required for
> +for hardware-accelerated video processing on Intel GEN Graphics devices
> +supported by the i915 driver, such as integrated Intel HD Graphics. It provides
> +access to both hardware and shader functionality for faster encoding, decoding,
> +and post-processing video formats like MPEG2, H.264/AVC, and VC-1.")
I suppose we should limit this driver to i686-linux and x86_64-linux only.
LGTM, looking forward to try it!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-07-27 18:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 3:27 [bug#36814] [PATCH 0/2] Add VA-API Intel back-end and utilities Tobias Geerinckx-Rice via Guix-patches
2019-07-26 3:30 ` [bug#36814] [PATCH 1/2] gnu: Add intel-vaapi-driver Tobias Geerinckx-Rice via Guix-patches
2019-07-26 3:30 ` [bug#36814] [PATCH 2/2] gnu: Add libva-utils Tobias Geerinckx-Rice via Guix-patches
2019-07-27 18:37 ` Marius Bakke
2019-07-27 18:35 ` Marius Bakke [this message]
2019-07-27 19:00 ` [bug#36814] [PATCH 1/2] gnu: Add intel-vaapi-driver Tobias Geerinckx-Rice via Guix-patches
2019-07-26 8:17 ` [bug#36814] [PATCH 0/2] Add VA-API Intel back-end and utilities Tobias Geerinckx-Rice via Guix-patches
2019-07-26 8:56 ` Jelle Licht
2019-07-26 17:58 ` Tobias Geerinckx-Rice via Guix-patches
2019-07-26 18:40 ` [bug#36814] [BONUS PATCH 3/2] gnu: intel-vaapi-driver: Provide LIBVA_DRIVERS_PATH Tobias Geerinckx-Rice via Guix-patches
2019-07-27 18:26 ` Marius Bakke
2019-07-27 18:50 ` Tobias Geerinckx-Rice via Guix-patches
2019-07-27 19:08 ` Tobias Geerinckx-Rice via Guix-patches
2019-07-27 19:16 ` Marius Bakke
2019-07-27 19:13 ` Marius Bakke
2019-07-27 21:29 ` bug#36814: [PATCH 0/2] Add VA-API Intel back-end and utilities Tobias Geerinckx-Rice via Guix-patches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877e83496t.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=36814@debbugs.gnu.org \
--cc=me@tobias.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).