From: "Balagopalakrishnan, Anand" <anandb@ti.com>
To: Denys Dmytriyenko <denys@konsulko.com>,
"Etheridge, Darren" <detheridge@ti.com>
Cc: "max.krummenacher@toradex.com" <max.krummenacher@toradex.com>,
"Eatmon, Ryan" <reatmon@ti.com>, "Sapp, Randolph" <rs@ti.com>,
"meta-ti@lists.yoctoproject.org" <meta-ti@lists.yoctoproject.org>
Subject: RE: [EXTERNAL] Re: [meta-ti][kirkstone][PATCH] mesa-pvr: rollback srcrev to unbreak Rogue GPU based platforms
Date: Wed, 22 Nov 2023 13:56:49 +0000 [thread overview]
Message-ID: <9fdb3c013e7a4c7f94f02a65a5f22661@ti.com> (raw)
In-Reply-To: <CAB2aN6Nsu7kJJmrC+v4NB=wg7h7CKxdkqGxDGQvnpydZsFUN3g@mail.gmail.com>
Denys,
I will send a different version of the patch shortly.
Regards,
Anand
-----Original Message-----
From: Denys Dmytriyenko <denys@konsulko.com>
Sent: Wednesday, November 22, 2023 3:28 AM
To: Etheridge, Darren <detheridge@ti.com>
Cc: max.krummenacher@toradex.com; Balagopalakrishnan, Anand <anandb@ti.com>; Eatmon, Ryan <reatmon@ti.com>; Sapp, Randolph <rs@ti.com>; meta-ti@lists.yoctoproject.org
Subject: [EXTERNAL] Re: [meta-ti][kirkstone][PATCH] mesa-pvr: rollback srcrev to unbreak Rogue GPU based platforms
I haven't seen this on the list - was this blocked?
As of the change itself - is this essentially unbreaking Rogue by breaking back SGX?
On Tue, Nov 21, 2023 at 11:50 AM Darren Etheridge <detheridge@ti.com> wrote:
>
> A bug was introduced while trying to unify the Mesa version that is used
> on SGX GPU's and Rogue GPU's. It manifests itself as an immediate segfault
> whenever you try and run something like glmark2-es2-wayland or
> weston-simple-egl on certain Rogue based platforms (specifically am62x).
>
> Rollback the SRCREV to a version before the Mesa SGX changes were added.
> While we figure out what the underlying issue is with the unified
> version.
>
> This reverts the mesa-pvr recipe back to be the equivalent of commit id:
> 21fb9cbc01390f362ca376891b9f96f2ad24f344
>
> Signed-off-by: Darren Etheridge <detheridge@ti.com>
> ---
> meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> 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 98d30c5b..281d6a21 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
> @@ -23,7 +23,7 @@ SRC_URI = " \
>
> S = "${WORKDIR}/git"
>
> -SRCREV = "7c9522a4147836064f582278e4f7115735c16868"
> +SRCREV = "54fd9d7dea098b6f11c2a244b0c6763dc8c5690c"
>
> PACKAGECONFIG:append = " \
> ${@bb.utils.contains('PREFERRED_PROVIDER_virtual/gpudriver',
> 'ti-img-rogue-driver', 'pvr', '', d)} \
> --
> 2.17.1
>
prev parent reply other threads:[~2023-11-22 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231121165038.6088-1-detheridge@ti.com>
2023-11-21 21:58 ` [meta-ti][kirkstone][PATCH] mesa-pvr: rollback srcrev to unbreak Rogue GPU based platforms Denys Dmytriyenko
2023-11-22 13:56 ` Balagopalakrishnan, Anand [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=9fdb3c013e7a4c7f94f02a65a5f22661@ti.com \
--to=anandb@ti.com \
--cc=denys@konsulko.com \
--cc=detheridge@ti.com \
--cc=max.krummenacher@toradex.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@ti.com \
--cc=rs@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).