| Message ID | 20250710093957.3740966-1-b-padhi@ti.com |
|---|---|
| State | Superseded |
| Delegated to: | Ryan Eatmon |
| Headers | show |
| Series | [master/scarthgap] meta-ti-bsp: linux-ti-staging-rt_6.12.bb: Add AM57xx RT branch | expand |
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}" 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 ''}
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 ''}
On 7/10/2025 10:06 AM, Denys Dmytriyenko wrote: > 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? We have "dropped" support for dra7xx, we do not build it or test it. > Also, not sure about RT on omapl128, but that's armv5. Same for omapl128. We are not really supporting or testing it anymore. So the list is just those three, which is why I suggested this path rather than the more generic one. > >> 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 ''}
On Thu, Jul 10, 2025 at 10:09:52AM -0500, Ryan Eatmon via lists.yoctoproject.org wrote: > > > On 7/10/2025 10:06 AM, Denys Dmytriyenko wrote: > >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? > > We have "dropped" support for dra7xx, we do not build it or test it. > > >Also, not sure about RT on omapl128, but that's armv5. > > Same for omapl128. We are not really supporting or testing it anymore. > > > So the list is just those three, which is why I suggested this path > rather than the more generic one. It's probably time to start removing unsupported machine configs, at least from the master, to avoid confusion. > >>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 ''}
On 7/10/2025 1:19 PM, Denys Dmytriyenko wrote: > On Thu, Jul 10, 2025 at 10:09:52AM -0500, Ryan Eatmon via lists.yoctoproject.org wrote: >> >> >> On 7/10/2025 10:06 AM, Denys Dmytriyenko wrote: >>> 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? >> >> We have "dropped" support for dra7xx, we do not build it or test it. >> >>> Also, not sure about RT on omapl128, but that's armv5. >> >> Same for omapl128. We are not really supporting or testing it anymore. >> >> >> So the list is just those three, which is why I suggested this path >> rather than the more generic one. > > It's probably time to start removing unsupported machine configs, at least > from the master, to avoid confusion. Agreed. I'll start that convo over here. > >>>> 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 ''}
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" + include ${@ 'recipes-kernel/linux/ti-extras-rt.inc' if d.getVar('TI_EXTRAS') else ''}
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(+)