From: pbui <pbui@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: chromium: update to 83.0.4103.116.
Date: Fri, 10 Jul 2020 19:38:48 +0200 [thread overview]
Message-ID: <20200710173848.zUqMfFww9PHJzy-_zdFqx3CxzKjBdnhfXDqdrrRMiOw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23511@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
New comment by pbui on void-packages repository
https://github.com/void-linux/void-packages/pull/23511#issuecomment-656798149
Comment:
@ericonr Yes, the old patch which @Duncaen is referring to (and removed in 06430645c61fe9ee0b8c052c6d58b0cd0bab4d61) enabled vaapi unconditionally. As noted in this commit message, this is no longer the case. First, we no longer have a big vaapi patch; vaapi support is now provided by upstream chromium. Second, vaapi is OFF by default. The user must explicitly choose to enable it. This should address the problem @Duncaen mentioned.
Note, I introduced this build option in 88464d1272e6a98f2a045169c07446a3181f5df9 and have been using it since then for my own machines. I am requesting to enable it by default because I believe it is stable now.
That said, I've only tested this on machines with Intel GPUs (both with it on and off). I'd be happy to wait for feedback from users with different devices.
Final note: Arch Linux has enabled vaapi by default in a similar manner as to what I am proposing here: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/chromium&id=0cbb8c4205a73ceb76066477fef42e55ae5aa394
next prev parent reply other threads:[~2020-07-10 17:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 16:54 [PR PATCH] " pbui
2020-07-10 17:02 ` ericonr
2020-07-10 17:38 ` pbui
2020-07-10 17:38 ` pbui [this message]
2020-07-10 21:22 ` jnbr
2020-07-10 23:21 ` [PR PATCH] [Updated] " pbui
2020-07-10 23:23 ` pbui
2020-07-11 9:34 ` jnbr
2020-07-16 18:15 ` [PR PATCH] [Merged]: " Johnnynator
2020-09-27 13:50 ` dm17
2020-09-27 14:41 ` pbui
2020-09-27 14:51 ` dm17
2020-09-27 15:12 ` pbui
2020-09-27 15:21 ` dm17
2020-09-27 17:23 ` dm17
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=20200710173848.zUqMfFww9PHJzy-_zdFqx3CxzKjBdnhfXDqdrrRMiOw@z \
--to=pbui@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).