From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: chromium: update to 83.0.4103.116.
Date: Thu, 16 Jul 2020 20:15:20 +0200 [thread overview]
Message-ID: <20200716181520.lqS7xud9weC8YDUbyIkIZ9lV2XM5HKPPwUMPUhuuj_g@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: 894 bytes --]
There's a merged pull request on the void-packages repository
chromium: update to 83.0.4103.116.
https://github.com/void-linux/void-packages/pull/23511
Description:
- Built for x86_64 and x86_64-musl.
- Tested on x86_64.
- Add sndio build option from #22888
- Turn on vaapi build option by default. With this build option, the
chromium package now supports VA-API for Intel and AMD GPUs.
However, users must opt-in to enabling this feature at run-time by
enabling "Override software rendering list" in chrome://flags or by
passing the --ignore-gpu-blacklist to chromium. Otherwise this
feature is disabled and not used.
This has been tested with YouTube on multiple machines with Intel GPUs.
- Add ffmpeg patch to workaround some problems with ffmpeg 4.3:
https://bugs.chromium.org/p/chromium/issues/detail?id=1095962
- Also update chromium-widevine.
next prev parent reply other threads:[~2020-07-16 18:15 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
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 ` Johnnynator [this message]
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=20200716181520.lqS7xud9weC8YDUbyIkIZ9lV2XM5HKPPwUMPUhuuj_g@z \
--to=johnnynator@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).