| Message ID | 20260603072932.1273938-2-m-shah@ti.com |
|---|---|
| State | New |
| Headers | show |
| Series | Fix NFS boot on K3 platforms with bsp-next kernel | expand |
On Wed, Jun 3, 2026 at 3:30 AM Moteen Shah via lists.yoctoproject.org <m-shah=ti.com@lists.yoctoproject.org> wrote: > AM65_CPSW_NUSS and its dependencies changed from built-in to loadable > modules in linux-next. Add them to TI_CORE_INITRAMFS_KERNEL_MODULES so > NFS boot continues to work on K3 platforms with the bsp-next kernel. > > Signed-off-by: Moteen Shah <m-shah@ti.com> > --- > meta-ti-bsp/conf/machine/include/k3.inc | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/meta-ti-bsp/conf/machine/include/k3.inc > b/meta-ti-bsp/conf/machine/include/k3.inc > index 6833789c..726c071f 100644 > --- a/meta-ti-bsp/conf/machine/include/k3.inc > +++ b/meta-ti-bsp/conf/machine/include/k3.inc > @@ -61,3 +61,9 @@ FALCON_INCLUDE = "" > FALCON_INCLUDE:ti-falcon = "conf/machine/include/ti-falcon.inc" > > require ${FALCON_INCLUDE} > + > +# AM65_CPSW_NUSS and its direct Kconfig dependencies became loadable > modules > +# in linux-next (post 7.1). Include them in the initramfs so NFS boot > works. > +# TI staging kernels (6.6/6.12/6.18) still have CPSW built-in (=y). > + > +TI_CORE_INITRAMFS_KERNEL_MODULES:append:bsp-next = " > kernel-module-ti-am65-cpsw-nuss kernel-module-k3-cppi-desc-pool > kernel-module-davinci-mdio kernel-module-ti-cpsw-ale > kernel-module-ti-cpsw-sl kernel-module-phylink kernel-module-mdio-bitbang > kernel-module-phy-gmii-sel" > Is there any way to link the inclusion of these kernel modules to the inclusion of the net boot recipe? If we don't need NFS boot support, how much larger does this make the initramfs? Just a thought. > -- > 2.34.1 > > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#19959): > https://lists.yoctoproject.org/g/meta-ti/message/19959 > Mute This Topic: https://lists.yoctoproject.org/mt/119625158/7902621 > Group Owner: meta-ti+owner@lists.yoctoproject.org > Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [ > jcormier@criticallink.com] > -=-=-=-=-=-=-=-=-=-=-=- > >
Hey Jon, On 03/06/26 19:55, Jon Cormier wrote: > > > On Wed, Jun 3, 2026 at 3:30 AM Moteen Shah via lists.yoctoproject.org > <http://lists.yoctoproject.org> <m-shah=ti.com@lists.yoctoproject.org> > wrote: > > AM65_CPSW_NUSS and its dependencies changed from built-in to loadable > modules in linux-next. Add them to TI_CORE_INITRAMFS_KERNEL_MODULES so > NFS boot continues to work on K3 platforms with the bsp-next kernel. > > Signed-off-by: Moteen Shah <m-shah@ti.com> > --- > meta-ti-bsp/conf/machine/include/k3.inc | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/meta-ti-bsp/conf/machine/include/k3.inc > b/meta-ti-bsp/conf/machine/include/k3.inc > index 6833789c..726c071f 100644 > --- a/meta-ti-bsp/conf/machine/include/k3.inc > +++ b/meta-ti-bsp/conf/machine/include/k3.inc > @@ -61,3 +61,9 @@ FALCON_INCLUDE = "" > FALCON_INCLUDE:ti-falcon = "conf/machine/include/ti-falcon.inc" > > require ${FALCON_INCLUDE} > + > +# AM65_CPSW_NUSS and its direct Kconfig dependencies became > loadable modules > +# in linux-next (post 7.1). Include them in the initramfs so NFS > boot works. > +# TI staging kernels (6.6/6.12/6.18) still have CPSW built-in (=y). > + > +TI_CORE_INITRAMFS_KERNEL_MODULES:append:bsp-next = " > kernel-module-ti-am65-cpsw-nuss kernel-module-k3-cppi-desc-pool > kernel-module-davinci-mdio kernel-module-ti-cpsw-ale > kernel-module-ti-cpsw-sl kernel-module-phylink > kernel-module-mdio-bitbang kernel-module-phy-gmii-sel" > > Is there any way to link the inclusion of these kernel modules to the > inclusion of the net boot recipe? If we don't need NFS boot support, > how much larger does this make the initramfs? Just a thought. I am seeing a size increase of 1MB in the uncompressed .cpio(88MBs -> 89MB's), I will look into the selective inclusion of the modules once, but I do thing it is necessary feature to have since the kernel is moving towards making those drivers m and we will need it as a part of base package. Regards, Moteen > > -- > 2.34.1 > > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#19959): > https://lists.yoctoproject.org/g/meta-ti/message/19959 > Mute This Topic: https://lists.yoctoproject.org/mt/119625158/7902621 > Group Owner: meta-ti+owner@lists.yoctoproject.org > <mailto:meta-ti%2Bowner@lists.yoctoproject.org> > Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub > [jcormier@criticallink.com] > -=-=-=-=-=-=-=-=-=-=-=- > > > > -- > Jonathan Cormier > Senior Software Engineer > > Office: 315.425.4045 x222 > > http://www.CriticalLink.com <http://www.criticallink.com/> > 6712 Brooklawn Parkway, Syracuse, NY 13211 >
diff --git a/meta-ti-bsp/conf/machine/include/k3.inc b/meta-ti-bsp/conf/machine/include/k3.inc index 6833789c..726c071f 100644 --- a/meta-ti-bsp/conf/machine/include/k3.inc +++ b/meta-ti-bsp/conf/machine/include/k3.inc @@ -61,3 +61,9 @@ FALCON_INCLUDE = "" FALCON_INCLUDE:ti-falcon = "conf/machine/include/ti-falcon.inc" require ${FALCON_INCLUDE} + +# AM65_CPSW_NUSS and its direct Kconfig dependencies became loadable modules +# in linux-next (post 7.1). Include them in the initramfs so NFS boot works. +# TI staging kernels (6.6/6.12/6.18) still have CPSW built-in (=y). + +TI_CORE_INITRAMFS_KERNEL_MODULES:append:bsp-next = " kernel-module-ti-am65-cpsw-nuss kernel-module-k3-cppi-desc-pool kernel-module-davinci-mdio kernel-module-ti-cpsw-ale kernel-module-ti-cpsw-sl kernel-module-phylink kernel-module-mdio-bitbang kernel-module-phy-gmii-sel"
AM65_CPSW_NUSS and its dependencies changed from built-in to loadable modules in linux-next. Add them to TI_CORE_INITRAMFS_KERNEL_MODULES so NFS boot continues to work on K3 platforms with the bsp-next kernel. Signed-off-by: Moteen Shah <m-shah@ti.com> --- meta-ti-bsp/conf/machine/include/k3.inc | 6 ++++++ 1 file changed, 6 insertions(+)