From: ja-cop <ja-cop@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Intel packages
Date: Fri, 28 Apr 2023 01:54:24 +0200 [thread overview]
Message-ID: <20230427235424.coyH_O0pNF8BJe5I5l7kZqgYKzBidPaCuAPHuNdb2z0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41132@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]
New comment by ja-cop on void-packages repository
https://github.com/void-linux/void-packages/pull/41132#issuecomment-1526787356
Comment:
Yeah, I have `libva` installed, and I think I managed to install all the packages from this PR too:
```bash
> xbps-query -l | egrep 'intel-gmmlib|intel-media-driver|onevpl|intel-media-sdk|igt-gpu-tools|ffmpeg|libva'
ii ffmpeg-4.4.3_3 Decoding, encoding and streaming software
ii ffmpeg-devel-4.4.3_2 Decoding, encoding and streaming software - development files
ii ffmpegthumbs-22.12.1_1 FFmpeg-based thumbnail creator for video files
ii igt-gpu-tools-1.26_1 Tools for development and testing of the DRM drivers
ii intel-gmmlib-22.3.3_1 Intel Graphics Memory Management Library
ii intel-gmmlib-devel-22.3.3_1 Intel Graphics Memory Management Library - development files
ii intel-media-driver-22.6.4_1 Intel Media Driver for VAAPI (Broadwell+)
ii intel-media-sdk-22.6.4_1 Intel Media SDK
ii libva-2.17.0_1 Video Acceleration (VA) API
ii libva-devel-2.17.0_1 Video Acceleration (VA) API - development files
ii libvamp-plugin-sdk-2.10.0_1 Vamp audio analysis plugin system - Runtime libraries
ii onevpl-2023.1.2_1 Intel oneAPI Video Processing library
ii onevpl-intel-gpu-22.6.4_1 Runtime implementation of oneVPL API for Intel Gen GPUs
```
next prev parent reply other threads:[~2023-04-27 23:54 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 14:40 [PR PATCH] [WIP] " zlice
2022-12-16 14:43 ` [PR PATCH] [Updated] " zlice
2022-12-16 14:45 ` zlice
2022-12-16 16:33 ` zlice
2022-12-16 17:27 ` zlice
2022-12-16 17:33 ` zlice
2022-12-16 18:11 ` zlice
2022-12-16 19:03 ` zlice
2022-12-16 21:37 ` zlice
2022-12-16 22:28 ` zlice
2022-12-18 5:29 ` [PR PATCH] [Updated] " zlice
2022-12-18 6:19 ` zlice
2022-12-18 6:25 ` zlice
2022-12-18 6:49 ` [PR PATCH] [Updated] " zlice
2022-12-18 11:31 ` classabbyamp
2022-12-18 15:41 ` [PR PATCH] [Updated] " zlice
2022-12-18 19:47 ` zlice
2022-12-19 3:02 ` zlice
2022-12-19 3:02 ` zlice
2022-12-20 15:10 ` zlice
2023-01-14 4:09 ` [PR PATCH] [Updated] " zlice
2023-01-14 4:15 ` zlice
2023-01-20 14:10 ` [PR PATCH] [Updated] " zlice
2023-01-20 15:48 ` icp1994
2023-01-20 16:00 ` zlice
2023-01-20 16:02 ` icp1994
2023-01-20 16:04 ` zlice
2023-01-25 11:29 ` Anachron
2023-01-25 12:50 ` icp1994
2023-01-26 11:05 ` Anachron
2023-02-08 9:08 ` Anachron
2023-02-08 9:10 ` Anachron
2023-02-08 9:11 ` Anachron
2023-02-08 12:25 ` zlice
2023-02-08 14:15 ` [PR PATCH] [Updated] " zlice
2023-02-08 14:21 ` zlice
2023-02-08 15:34 ` zlice
2023-02-08 15:54 ` zlice
2023-02-08 15:55 ` [PR PATCH] [Updated] " zlice
2023-02-08 15:57 ` zlice
2023-02-10 7:18 ` icp1994
2023-02-10 7:20 ` icp1994
2023-03-23 13:32 ` [PR PATCH] [Updated] " zlice
2023-03-23 13:33 ` zlice
2023-04-27 17:45 ` ja-cop
2023-04-27 18:01 ` zlice
2023-04-27 18:02 ` zlice
2023-04-27 22:10 ` ja-cop
2023-04-27 23:43 ` zlice
2023-04-27 23:54 ` ja-cop [this message]
2023-04-28 13:38 ` zlice
2023-04-28 15:56 ` ja-cop
2023-05-05 12:52 ` [PR PATCH] [Updated] " zlice
2023-05-05 12:53 ` zlice
2023-05-22 15:56 ` [PR PATCH] [Updated] " zlice
2023-05-22 15:58 ` zlice
2023-06-19 20:21 ` [PR PATCH] [Updated] " zlice
2023-06-20 6:52 ` Anachron
2023-06-20 10:43 ` zlice
2023-06-22 12:23 ` zlice
2023-06-22 12:23 ` [PR PATCH] [Updated] " zlice
2023-07-04 15:23 ` zlice
2023-07-04 15:24 ` zlice
2023-07-04 17:17 ` Anachron
2023-08-02 14:01 ` [PR PATCH] [Updated] " zlice
2023-11-01 1:46 ` github-actions
2023-11-15 1:46 ` [PR PATCH] [Closed]: " github-actions
2023-11-20 12:54 ` zlice
2024-01-10 22:49 ` mdkcore0
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230427235424.coyH_O0pNF8BJe5I5l7kZqgYKzBidPaCuAPHuNdb2z0@z \
--to=ja-cop@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).