From: daniel-eys <daniel-eys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Update Intel VA-API drivers
Date: Sat, 03 Oct 2020 00:51:56 +0200 [thread overview]
Message-ID: <20201002225156.Ue0KGsKzRzUWxFl2OneLDZM9ntAChmMeuy36ADXcZOo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25288@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
New comment by daniel-eys on void-packages repository
https://github.com/void-linux/void-packages/pull/25288#issuecomment-702990202
Comment:
* Let's not forget about `libva-glx` and have it back in sync with `libva`.
* We could probably update `libva-utils` as well, just to have the whole vaapi stack updated.
* `libva-intel-driver`:
* I can confirm this working on an Intel Ivybridge with glibc.
* The `CFLAGS="-fcommon"` shouldn't be necessary anymore, looks like upstream fixed gcc10 issues [not verified though, just read the change/gitlog].
* The python2 sed in `pre_configure()` looks obsolete.
next prev parent reply other threads:[~2020-10-02 22:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 19:34 [PR PATCH] intel-media-driver: update to 20.3.0 (and dep) st3r4g
2020-10-02 20:00 ` ericonr
2020-10-02 21:21 ` ericonr
2020-10-02 21:48 ` st3r4g
2020-10-02 21:56 ` [PR PATCH] [Updated] " st3r4g
2020-10-02 22:11 ` [PR REVIEW] Update Intel VA-API drivers ericonr
2020-10-02 22:51 ` daniel-eys [this message]
2020-10-02 23:00 ` st3r4g
2020-10-02 23:08 ` ericonr
2020-10-06 9:15 ` [PR PATCH] [Updated] " st3r4g
2020-10-06 9:24 ` st3r4g
2020-10-06 9:29 ` st3r4g
2020-10-14 5:14 ` travankor
2020-10-14 6:49 ` st3r4g
2020-10-16 5:31 ` travankor
2020-10-16 5:33 ` travankor
2020-10-16 5:33 ` travankor
2020-10-16 5:35 ` travankor
2020-10-16 6:02 ` travankor
2020-10-16 6:02 ` travankor
2020-10-16 11:18 ` st3r4g
2020-10-16 15:05 ` travankor
2020-10-16 15:10 ` travankor
2020-10-16 17:17 ` ericonr
2020-10-16 17:20 ` ericonr
2020-10-16 17:21 ` ericonr
2020-10-17 2:40 ` [PR PATCH] [Closed]: " ericonr
2020-10-17 2:42 ` ericonr
2020-10-17 6:20 ` st3r4g
2020-10-17 6:29 ` st3r4g
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=20201002225156.Ue0KGsKzRzUWxFl2OneLDZM9ntAChmMeuy36ADXcZOo@z \
--to=daniel-eys@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).