From: Randolph Sapp <rs@ti.com>
To: Max Krummenacher <max.oss.09@gmail.com>, <denis@denix.org>,
<reatmon@ti.com>
Cc: <meta-ti@lists.yoctoproject.org>
Subject: Re: [meta-ti][master/scarthgap][PATCH] ti-img-rogue-driver_23.3.6512818: gcc 14 compat
Date: Fri, 21 Jun 2024 18:41:41 -0500 [thread overview]
Message-ID: <D263CWRYKX4V.3GE2GCYVA30PC@ti.com> (raw)
In-Reply-To: <7b58709f8ab387300f300e9d2dab96b81639d5cf.camel@gmail.com>
On Fri Jun 21, 2024 at 5:41 PM CDT, Max Krummenacher wrote:
> Hello Randolph
>
> Am Freitag, dem 21.06.2024 um 15:15 -0500 schrieb rs@ti.com:
> > From: Randolph Sapp <rs@ti.com>
> >
> > Bump this recipe to add a change to help with GCC 14 compatibility in
> > the check-cc script used to check compiler flags before use.
> >
> > Also ports some of the patches that were added to the kirkstone branch
> > post creation of what was supposed to be a temporary scarthgap branch.
> >
> > Signed-off-by: Randolph Sapp <rs@ti.com>
> > ---
> >
> > Sorry for the delay. Needed to run some tests since there were some other
> > patches that had not been ported to the intermediary branch.
> >
> > .../powervr-drivers/ti-img-rogue-driver_23.3.6512818.bb | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta-ti-bsp/recipes-bsp/powervr-drivers/ti-img-rogue-driver_23.3.6512818.bb b/meta-ti-bsp/recipes-bsp/powervr-drivers/ti-img-rogue-driver_23.3.6512818.bb
> > index 34c22cb2..7fbb0524 100644
> > --- a/meta-ti-bsp/recipes-bsp/powervr-drivers/ti-img-rogue-driver_23.3.6512818.bb
> > +++ b/meta-ti-bsp/recipes-bsp/powervr-drivers/ti-img-rogue-driver_23.3.6512818.bb
> > @@ -19,7 +19,7 @@ SRC_URI = "git://git.ti.com/git/graphics/ti-img-rogue-driver.git;protocol=https;
> >
> > S = "${WORKDIR}/git"
> >
> > -SRCREV = "2f409b4dd2540e896b54bff02219d4fc51129b81"
> > +SRCREV = "97727f8606ca984527a470252c0bc3ada1bb3f92"
>
> This SHA is not (yet ?) in the repository.
> I tried with latest HEAD, i.e. 7b04fd4a24fe. That builds fine in my setup. Thanks for the quick fix.
>
> Max
Hold on. Just realized the bsp provider logic that's supposed to be selecting
this recipe thinks this is a compatible driver for kernel 6.1. It's not.
This branch was an intermediary branch for kernel 6.6. There were dt changes
made for AM62 that make it incompatible. Have to update the old kirkstone branch
and reset this recipe to point at that.
Thankfully that means I can finally delete the intermediary 6.6-23.3 branch
since that's not officially supported by anyone...
- Randolph
> >
> > TARGET_PRODUCT:j721e = "j721e_linux"
> > TARGET_PRODUCT:j721s2 = "j721s2_linux"
prev parent reply other threads:[~2024-06-21 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 20:15 [meta-ti][master/scarthgap][PATCH] ti-img-rogue-driver_23.3.6512818: gcc 14 compat rs
2024-06-21 22:41 ` Max Krummenacher
2024-06-21 23:41 ` Randolph Sapp [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=D263CWRYKX4V.3GE2GCYVA30PC@ti.com \
--to=rs@ti.com \
--cc=denis@denix.org \
--cc=max.oss.09@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.