From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: mesa: update to 20.2.1
Date: Thu, 15 Oct 2020 23:11:48 +0200 [thread overview]
Message-ID: <20201015211148.x0wbg0Z3LDF7gtwgfd_GOH4-PwmlfhLlWzq7uMR03oM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25318@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 853 bytes --]
There's a merged pull request on the void-packages repository
mesa: update to 20.2.1
https://github.com/void-linux/void-packages/pull/25318
Description:
This updates mesa to 20.2.0
Several things to keep in mind:
Announcement happened only on their mailing list https://lists.freedesktop.org/archives/mesa-announce/2020-September/000600.html
20.1.9 was released later but new games may still need 20.2.x to work.
I tested compiling musl and hope this does not cause run time problems for NVIDIA or Intel graphic cards.
The game Horizon Zero Dawn actually runs with 20.2.0 for me (on 20.1.9 and lower the game crashes during the intro or within seconds at the main menu.
I have checked this on one game so far. I'll test it on other games in the next hours (Radeon RX 590).
It would be nice if others would check it on their setups.
prev parent reply other threads:[~2020-10-15 21:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 17:07 [PR PATCH] [REQUIRES TESTS] mesa: update to 20.2.0 Ophidiophobia
2020-10-03 18:08 ` q66
2020-10-03 18:10 ` q66
2020-10-03 19:06 ` Ophidiophobia
2020-10-04 6:36 ` [PR PATCH] [Updated] " Ophidiophobia
2020-10-04 6:58 ` Ophidiophobia
2020-10-04 9:58 ` Ophidiophobia
2020-10-04 10:32 ` q66
2020-10-05 5:37 ` [PR PATCH] [Updated] " Ophidiophobia
2020-10-09 14:12 ` HadetTheUndying
2020-10-15 14:31 ` [PR PATCH] [Updated] " Ophidiophobia
2020-10-15 14:42 ` Ophidiophobia
2020-10-15 15:12 ` mesa: update to 20.2.1 Ophidiophobia
2020-10-15 21:11 ` q66 [this message]
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=20201015211148.x0wbg0Z3LDF7gtwgfd_GOH4-PwmlfhLlWzq7uMR03oM@z \
--to=q66@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).