From: HanoJing <HanoJing@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Reason for deletion of srcpkgs/mesa/patches/0001-radeonsi-On-Aarch64-force-persistent-buffers-to-GTT.patch ?
Date: Thu, 16 Jun 2022 20:35:24 +0200 [thread overview]
Message-ID: <20220616183524.fWek8QQpuljoIt5GM-PTA7Cqea44faXLlI9Ic0O_-Kg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37579@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
Closed issue by HanoJing on void-packages repository
https://github.com/void-linux/void-packages/issues/37579
Description:
### System
motherboard: SolidRun HoneyComb LX2K
CPU: NXP LayerScape LX2160A
Graphicscard: AMD Radeon RX580 XFX
affects mesa versions: all
### Expected behavior
mesa doesn't cause graphics corruption like normal
### Actual behavior
mesa causes graphics corruption
### Steps to reproduce the behavior
have mesa instlalled on a HoneyComb LX2K for instance, running Void Linux, use Xorg, use mesa dependent programs.
#############################
What is the reason for the deletion of srcpkgs/mesa/patches/0001-radeonsi-On-Aarch64-force-persistent-buffers-to-GTT.patch ?
As a user of the SolidRun HoneyComb LX2K, I get graphics corruption.
This said patch is needed to the fix of the graphics corruption.
kind regards,
HanoJing
next prev parent reply other threads:[~2022-06-16 18:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 21:22 [ISSUE] " HanoJing
2022-06-16 1:33 ` abenson
2022-06-16 7:44 ` HanoJing
2022-06-16 7:58 ` paper42
2022-06-16 11:01 ` HanoJing
2022-06-16 11:26 ` HanoJing
2022-06-16 11:36 ` HanoJing
2022-06-16 11:36 ` HanoJing
2022-06-16 12:06 ` HanoJing
2022-06-16 12:24 ` HanoJing
2022-06-16 12:27 ` HanoJing
2022-06-16 12:56 ` HanoJing
2022-06-16 12:57 ` HanoJing
2022-06-16 14:00 ` abenson
2022-06-16 14:02 ` abenson
2022-06-16 14:04 ` abenson
2022-06-16 16:49 ` HanoJing
2022-06-16 16:51 ` HanoJing
2022-06-16 16:57 ` abenson
2022-06-16 17:18 ` HanoJing
2022-06-16 18:35 ` HanoJing
2022-06-16 18:35 ` HanoJing [this message]
2022-06-16 19:17 ` HanoJing
2022-06-16 19:18 ` HanoJing
2022-06-16 19:32 ` HanoJing
2022-06-16 19:34 ` HanoJing
2022-06-16 19:35 ` HanoJing
2022-06-16 19:45 ` abenson
2022-06-16 20:12 ` HanoJing
2022-06-16 21:27 ` HanoJing
2022-06-16 21:29 ` HanoJing
2022-06-16 21:34 ` HanoJing
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=20220616183524.fWek8QQpuljoIt5GM-PTA7Cqea44faXLlI9Ic0O_-Kg@z \
--to=hanojing@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).