This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PROCESSOR-SDK-AM62X: linux kernel update schedule

Genius 3186 points
Part Number: PROCESSOR-SDK-AM62X


Tool/software:

Hi

May I have question about SDK update plan?

My custmer want to use newest version of LTS kernel for develop, because security.

But now, Processor SDK 9.02.01.10 is using 6.1.83 (newest is 6.1.102 in kernel.org)

How often is the Yocto SDK updated? 

--

And if Debian using, "apt update" and "apt upgrade"command will update own kernel to ti-git version?

https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?h=linux-6.1.y

--

And, Is the newest version kernel in ti-git can use with Yocto-SDK 9.02's BSP? 

Thanks

GR

  • Hi,

    Our expert is currently out of office and responses will be delayed. In general, we move to a new Kernel LTS and Yocto LTS once a year. Our next SDK will be based on Scarthgap and Kernel 6.6. 

    Regards,
    Krunal

  • Krunal:  Linux Kernel 6.6. LTS in the AM62x & AM64x SDKs ver 10 ? 

  • Yes, that's correct and for more information, please feel free to refer to the following: https://git.ti.com/cgit/arago-project/oe-layersetup/tree/configs/arago-scarthgap-config.txt. The timelines are still not finalized but our dev team are working on those branches. 

    Regards,
    Krunal

  • Hi Krunal,

    Thanks for your information.

    Our expert is currently out of office and responses will be delayed. In general, we move to a new Kernel LTS and Yocto LTS once a year. Our next SDK will be based on Scarthgap and Kernel 6.6. 

    I understand that migrating majior version Update is per Year.

    I want to know Update plan of miner version of LTS kernel.

    Especially, now newst version of Kernel 6.1 is 6.1.83, but Kernel.org released 6.1.10x.

    https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?h=ti-linux-6.1.y&id=e5cd595e23c1a075359a337c0e5c3a4f2dc28dd1

    https://www.kernel.org/

    I want to know when is updated.

    Best regards,

    GR 

  • As a rule of thumb the Kernel is usually re-synced with the upstream LTS kernel as the team prepares for each point release (e.g., SDK v10.1., 10.2, ...). You can see this scheme when you look at the merge commits of the kernel tree.

    Regards, Andreas

  • Hi Andreas,

    I am sorry for late reply due to Japanese holiday.

    As a rule of thumb the Kernel is usually re-synced with the upstream LTS kernel as the team prepares for each point release (e.g., SDK v10.1., 10.2, ...). You can see this scheme when you look at the merge commits of the kernel tree.

    I understand each SDK miner release will update kernel miner version.

    And it seems released SDK v10.x.x.

    Is this mean kernel 6.1.10x does not will be ti-linux?

    Kernek 6.1.x latest miner version was / will been 6.1.83?

    Thanks,

    GR

  • Kernek 6.1.x latest miner version was / will been 6.1.83?

    Yes that's the current/latest version of the ti-linux-6.1.y tree https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/Makefile?h=ti-linux-6.1.y#n2

    As there are no more planned updates/release to the v9.x series of SDKs, this will almost certainly be the final version of this Kernel branch. You can also see this from the fact that it was last updated 3 months ago.

    If you want to continue using a 6.1 based kernel you can merge additional/newer minor kernel versions yourself into this tree, taken from https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-6.1.y   I've tried the same, see below. It (mostly) works seamlessly but there's a couple of merge conflicts that need to be resolved manually.


    $ git remote -v
    stable  https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git (fetch)
    stable  https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git (push)
    ti      https://git.ti.com/git/ti-linux-kernel/ti-linux-kernel.git (fetch)
    ti      https://git.ti.com/git/ti-linux-kernel/ti-linux-kernel.git (push)
    
    # Create new branch to continue evolving the TI tree based using 'stable'
    $ git checkout -b ti-linux-6.1.y-stable ti/ti-linux-6.1.y
    Updating files: 100% (43473/43473), done.
    Branch 'ti-linux-6.1.y-stable' set up to track remote branch 'ti-linux-6.1.y' from 'ti'.
    Switched to a new branch 'ti-linux-6.1.y-stable'
    
    # Merge the latest 'stable' tree with the TI tree
    # The merge goes mostly well, but there are a handful of conflicts that need to
    # get resolved manually. See `git status` for details.
    $ git merge stable/linux-6.1.y
    Auto-merging MAINTAINERS
    Auto-merging Makefile
    Auto-merging drivers/counter/ti-eqep.c
    CONFLICT (content): Merge conflict in drivers/counter/ti-eqep.c
    Auto-merging drivers/cpufreq/ti-cpufreq.c
    Auto-merging drivers/dma/ti/k3-udma.c
    CONFLICT (content): Merge conflict in drivers/dma/ti/k3-udma.c
    Auto-merging drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-core.c
    Auto-merging drivers/gpu/drm/bridge/panel.c
    Auto-merging drivers/gpu/drm/drm_bridge.c
    Auto-merging drivers/gpu/drm/panel/panel-edp.c
    Auto-merging drivers/gpu/drm/panel/panel-ilitek-ili9881c.c
    Auto-merging drivers/gpu/drm/panel/panel-simple.c
    Auto-merging drivers/mfd/Makefile
    Auto-merging drivers/mmc/host/sdhci_am654.c
    CONFLICT (content): Merge conflict in drivers/mmc/host/sdhci_am654.c
    Auto-merging drivers/net/ethernet/freescale/fec_ptp.c
    Auto-merging drivers/net/ethernet/ti/am65-cpsw-nuss.c
    Auto-merging drivers/net/ethernet/ti/am65-cpts.c
    Auto-merging drivers/pci/controller/dwc/pci-keystone.c
    CONFLICT (content): Merge conflict in drivers/pci/controller/dwc/pci-keystone.c
    Auto-merging drivers/pci/pcie/aspm.c
    Auto-merging drivers/phy/cadence/phy-cadence-torrent.c
    Auto-merging drivers/pinctrl/pinctrl-single.c
    Auto-merging drivers/remoteproc/ti_k3_r5_remoteproc.c
    CONFLICT (content): Merge conflict in drivers/remoteproc/ti_k3_r5_remoteproc.c
    Auto-merging drivers/tty/serial/8250/8250_omap.c
    Auto-merging drivers/usb/dwc3/core.c
    Auto-merging drivers/usb/dwc3/dwc3-am62.c
    CONFLICT (content): Merge conflict in drivers/usb/dwc3/dwc3-am62.c
    Auto-merging drivers/usb/typec/tipd/core.c
    Auto-merging drivers/watchdog/rti_wdt.c
    Auto-merging include/sound/dmaengine_pcm.h
    CONFLICT (content): Merge conflict in include/sound/dmaengine_pcm.h
    Auto-merging net/hsr/hsr_device.c
    Auto-merging scripts/Makefile.build
    Auto-merging scripts/Makefile.lib
    Auto-merging sound/core/pcm_dmaengine.c
    CONFLICT (content): Merge conflict in sound/core/pcm_dmaengine.c
    Auto-merging sound/soc/soc-generic-dmaengine-pcm.c
    CONFLICT (content): Merge conflict in sound/soc/soc-generic-dmaengine-pcm.c
    Auto-merging sound/soc/ti/davinci-mcasp.c
    CONFLICT (content): Merge conflict in sound/soc/ti/davinci-mcasp.c
    Automatic merge failed; fix conflicts and then commit the result.

    Regards, Andreas

  • Andreas,

    Thank you for the information!

    GR