From: Denys Dmytriyenko <denis@denix.org>
To: reatmon@ti.com
Cc: Beleswar Padhi <b-padhi@ti.com>,
denys@konsulko.com, a-limaye@ti.com, afd@ti.com, u-kumar1@ti.com,
meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti] [master/scarthgap][PATCH] meta-ti-bsp: linux-ti-staging-rt_6.12.bb: Add AM57xx RT branch
Date: Thu, 10 Jul 2025 11:06:05 -0400 [thread overview]
Message-ID: <20250710150605.GV18383@denix.org> (raw)
In-Reply-To: <997eff48-8faf-4da4-ac90-29b49a5589e8@ti.com>
On Thu, Jul 10, 2025 at 09:32:51AM -0500, Ryan Eatmon via lists.yoctoproject.org wrote:
>
>
> On 7/10/2025 4:39 AM, Beleswar Padhi wrote:
> >While all other devices use the same branch for RT and non-RT builds,
> >the AM57xx ARM32 devices have a separate branch for RT Kernel which is
> >"ti-rt-linux-6.12.y-arm32". Update the BRANCH and SRCREV for am57xx
> >device family for RT builds.
> >
> >Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
> >---
> > meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.12.bb | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> >diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.12.bb b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.12.bb
> >index 9e5c4ee4..e78f046d 100644
> >--- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.12.bb
> >+++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.12.bb
> >@@ -6,4 +6,7 @@ KERNEL_LOCALVERSION:append = "-rt"
> > # This will have priority over generic non-rt path
> > FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}-6.12:"
> >+BRANCH:am57xx = "ti-rt-linux-6.12.y-arm32"
> >+SRCREV:am57xx = "f0e4f5ca0905956c70779b31663f594c08c6a3bc"
>
> NAK.
>
> This is applies to all 32bit platforms, not just am57xx. So the
> mechanism needs to be done in a way to support that.
>
> BRANCH_32BIT = "ti-rt-linux-6.12.y-arm32"
> SRCREV_32BIT = "f0e4f5ca0905956c70779b31663f594c08c6a3bc"
>
> BRANCH:ti33x = "${BRANCH_32BIT}"
> BRANCH:ti43x = "${BRANCH_32BIT}"
> BRANCH:am57xx = "${BRANCH_32BIT}"
>
> SRCREV:ti33x = "${SRCREV_32BIT}"
> SRCREV:ti43x = "${SRCREV_32BIT}"
> SRCREV:am57xx = "${SRCREV_32BIT}"
What about dra7xx? Why not simply use armv7a override?
Also, not sure about RT on omapl128, but that's armv5.
> Also, update the commit message to not be am57 specific.
>
> And in the subject, we don't need the meta-ti-bsp or the .bb:
>
> [master/scarthgap][PATCH] linux-ti-staging-rt_6.12: Add 32bit RT branch
>
> Keep the subject shorter when possible
>
> > include ${@ 'recipes-kernel/linux/ti-extras-rt.inc' if d.getVar('TI_EXTRAS') else ''}
next prev parent reply other threads:[~2025-07-10 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 9:39 [master/scarthgap][PATCH] meta-ti-bsp: linux-ti-staging-rt_6.12.bb: Add AM57xx RT branch Beleswar Padhi
2025-07-10 14:32 ` Ryan Eatmon
2025-07-10 15:06 ` Denys Dmytriyenko [this message]
2025-07-10 15:09 ` [meta-ti] " Ryan Eatmon
2025-07-10 18:19 ` Denys Dmytriyenko
2025-07-10 18:43 ` Ryan Eatmon
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=20250710150605.GV18383@denix.org \
--to=denis@denix.org \
--cc=a-limaye@ti.com \
--cc=afd@ti.com \
--cc=b-padhi@ti.com \
--cc=denys@konsulko.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@ti.com \
--cc=u-kumar1@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.