From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: mesa: update to 22.0.4
Date: Mon, 13 Jun 2022 05:35:13 +0200 [thread overview]
Message-ID: <20220613033513.6AgP4nMYJPAfpb3qJdFS0QYcXmorv61niWJS74gB_NA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36961@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
There's a closed pull request on the void-packages repository
mesa: update to 22.0.4
https://github.com/void-linux/void-packages/pull/36961
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
Performance seems better? May be placebo.
#### Local build testing
- I built this PR locally for my native architecture, x86_64
#### Comments
Tested this on Intel i7-6700k iGPU and AMD 5700. It looks like older cards are being dropped and the build complains about some "amber" branch? Project "amber"? I don't know what that is in Mesa land. Looks like i915/i965 are dropped but my 6700k said it was using 'iris' graphics. [Gentoo's wiki](https://wiki.gentoo.org/wiki/Intel) has a table that shows Haswell (Intel 4xxx CPUs) are the last to not support iris driver.
I'm sure there are people who know way more than me about Mesa's changes. Just figured I'd put this here since it seems to be working.
next prev parent reply other threads:[~2022-06-13 3:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 19:37 [PR PATCH] [WIP] mesa: update to 22.0.2 zlice
2022-05-02 21:03 ` [PR PATCH] [Updated] " zlice
2022-05-02 21:09 ` zlice
2022-05-02 21:22 ` zlice
2022-05-02 21:46 ` zlice
2022-05-06 0:33 ` tsndqst
2022-05-06 21:23 ` [PR REVIEW] " tsndqst
2022-05-06 21:25 ` [PR PATCH] [Updated] " zlice
2022-05-07 6:09 ` wundrweapon
2022-05-07 11:56 ` zlice
2022-05-07 19:56 ` wundrweapon
2022-05-07 20:53 ` wundrweapon
2022-05-09 2:42 ` HadetTheUndying
2022-05-14 20:59 ` [PR PATCH] [Updated] " zlice
2022-05-14 21:20 ` [PR REVIEW] " tsndqst
2022-05-14 23:10 ` [PR PATCH] [Updated] " zlice
2022-05-15 12:32 ` mesa: update to 22.0.3 zlice
2022-05-21 12:02 ` HadetTheUndying
2022-05-21 14:42 ` [PR PATCH] [Updated] " zlice
2022-05-23 15:20 ` mesa: update to 22.0.4 zlice
2022-05-26 3:35 ` RicArch97
2022-06-01 17:25 ` sug0
2022-06-01 17:27 ` zlice
2022-06-02 12:32 ` [PR REVIEW] " ericonr
2022-06-02 12:32 ` ericonr
2022-06-02 12:35 ` zlice
2022-06-02 12:41 ` zlice
2022-06-02 12:47 ` sug0
2022-06-02 12:59 ` RicArch97
2022-06-02 14:24 ` [PR PATCH] [Updated] " zlice
2022-06-02 14:25 ` [PR REVIEW] " zlice
2022-06-13 3:35 ` abenson [this message]
2022-06-13 11:50 ` zlice
2022-06-13 13:17 ` RicArch97
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=20220613033513.6AgP4nMYJPAfpb3qJdFS0QYcXmorv61niWJS74gB_NA@z \
--to=abenson@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).