From: <rs@ti.com>
To: <denys@konsulko.com>, <reatmon@ti.com>, <detheridge@ti.com>
Cc: <meta-ti@lists.yoctoproject.org>
Subject: [meta-ti][kirkstone/master][PATCH] mesa-pvr: bump srcrev and drop conditional logic
Date: Fri, 26 Jan 2024 13:04:16 -0600 [thread overview]
Message-ID: <20240126190416.1368711-1-rs@ti.com> (raw)
From: Randolph Sapp <rs@ti.com>
Bump the SRCREV to include some useful patches that:
- Fix the ROGUE segfault issue introduced by SGX (this was what
the old conditional logic was addressing)
- Fix destruction of event queue with proxies still attached
Signed-off-by: Randolph Sapp <rs@ti.com>
---
meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb b/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb
index 554fadd3..5abd0793 100644
--- a/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb
+++ b/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb
@@ -28,11 +28,7 @@ PACKAGECONFIG:append = " \
${@bb.utils.contains('PREFERRED_PROVIDER_virtual/gpudriver', 'ti-sgx-ddk-km', 'sgx', '', d)} \
"
-# Temporary work around to use a different SRCREV for SGX Mesa, vs Rogue Mesa
-# Idea is these two should be the same, but currently a segfault is happening
-# on certain platforms if the sgx commit is used.
-SRCREV = "${@bb.utils.contains('PACKAGECONFIG', 'sgx', '7c9522a4147836064f582278e4f7115735c16868', '54fd9d7dea098b6f11c2a244b0c6763dc8c5690c', d)}"
-PR = "sgxrgx${SRCPV}"
+SRCREV = "1be98ba80452ebe38546a7fca26b5a70f2629083"
PVR_DISPLAY_CONTROLLER_ALIAS ??= "tidss"
PACKAGECONFIG[pvr] = "-Dgallium-pvr-alias=${PVR_DISPLAY_CONTROLLER_ALIAS},"
--
2.43.0
next reply other threads:[~2024-01-26 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 19:04 rs [this message]
2024-02-01 22:34 ` [meta-ti][kirkstone/master][PATCH] mesa-pvr: bump srcrev and drop conditional logic Etheridge, Darren
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=20240126190416.1368711-1-rs@ti.com \
--to=rs@ti.com \
--cc=denys@konsulko.com \
--cc=detheridge@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@ti.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).