AM5728: AM5728 Linux SDK Roadmap and Kernel Upgrade Strategy

Hello Shiv Rai ,

The latest SDK 11.1 (<-- see release notes) is the last official SDK release from TI for AM57xx. The model will change into only internal releases that can be shared with the customer as part of our internal CI/CD process.

As part of TI’s commitment to use the community supported long term stable releases, we have updated the AM57 Processor SDK 11.1 release to latch on to the Linux kernel version 6.12 which is identified for super long-term stable(SLTS) kernel.

SLTS kernel 6.12 will be supported till Mid-2035, by CIP project. Customers may directly engage with CIP for super long-term support.

In upstream, AM57x is supported, and TI is committed to maintain this platform in upstream code branches

Most of features are available in upstream code base and remaining features TI is committed to upstream (These features pulled into SDK while upstreaming is in progress)

• PRU/HSR/PRP support Upstreaming in progress[1] Target 4Q 2026
• VIP driver support – Already up-streamed
• Early boot and late attach support – In progress
  

These modules above are the major differences. I will have to ask our development team for information on Linux 7.x, but i believe the CIP comment above is the plan.

-Josue

Dear TI Support Team,

Thank you for the detailed response regarding the AM57xx software roadmap, the transition to the CIP 6.12 SLTS kernel baseline, and the upcoming Q4 2026 upstreaming targets.

To help us finalize our long-term product maintenance architecture and clarify our internal engineering resource allocation, we have two specific follow-up questions regarding the future support delivery model:

1. Clarification on "Internal Releases via CI/CD Process"

You mentioned that future software models will shift to internal releases shared with customers as part of TI's internal CI/CD process.

• Could you clarify the eligibility criteria to access these internal CI/CD releases? Are these builds available to all commercial customers developing on the AM57xx platform, or are they restricted based on target production volume/account tier?

• What are the formal technical or account requirements required to ensure our engineering team is included in this distribution pipeline?

2. Maintenance Responsibility for the ti-linux-6.12.y Branch

Regarding the Super Long-Term Stable (SLTS) 6.12 kernel baseline:

• Will Texas Instruments actively maintain and push periodic stable/security updates (backported from the CIP/mainline stable community) directly into the public ti-linux-6.12.y git branch at git.ti.com?

• Alternatively, should customers expect that the current branch is functionally frozen from TI's side, meaning we are expected to manually pull, merge, and test CIP security updates/patches into our local kernel tree ourselves?

Our objective is to ensure we align our engineering pipelines smoothly with TI's updated delivery workflows. Thank you for your continued guidance.

Best regards,

We have ported our changes to the linux-4.19.94+gitAUTOINC+be5389fd85-gbe5389fd85 kernel from TI Linux SDK 6.03 for our AM5728 SoC-based custom board. However, according to CVE Details, this kernel version is associated with a large number of reported CVEs.

You previously suggested addressing these vulnerabilities by backporting the relevant fixes from the CIP (Civil Infrastructure Platform) 4.19.x kernel branch. I have a couple of questions regarding this approach:

1. Since there are so many CVEs listed for Linux 4.19.x, how can we determine which vulnerabilities are actually relevant to our custom board and its specific configuration?
   
2. Once the applicable CVEs have been identified, what is the recommended process for locating the corresponding fixes in the CIP 4.19.x branch and backporting them to our kernel (linux-4.19.94+gitAUTOINC+be5389fd85-gbe5389fd85)?
   
3. Are there any tools or methodologies that can help automate or simplify the identification of applicable CVEs and the mapping of fixes to the CIP branch?
   

Any guidance on the recommended workflow would be greatly appreciated.

Shiv Rai ,

Thank you for your detailed questions regarding CVE management.

We do not have formal recommendations or documented processes for CVE triage, CIP branch fix mapping, or backporting methodology for customer-modified kernels. This falls outside the scope of TI's standard support for the SDK.

That said, we can connect you with a third-party specialist who works in this area and may be able to provide the hands-on guidance you need. If you'd like an
introduction, let us know and we'll make that connection.

-Josue

Josue Zamitiz-Ayala said:

Most of features are available in upstream code base and remaining features TI is committed to upstream (These features pulled into SDK while upstreaming is in progress)

• PRU/HSR/PRP support Upstreaming in progress[1] Target 4Q 2026
• VIP driver support – Already up-streamed

Does that mean that whatever that used to work in 4.19.94 kernel (except graphics related which has been deprecated in later SDK versions ) would also work in 7.x upstream kernel (in which TI has commited its changes)? Also tell which 7.x version need to download from kernel.org ? Latest stable non-LTS version is 7.1.3 on kernel.org. Please tell as early as possible !

Thanks! 

Hello,
Thank you for your inquiry. **Josue Zamitiz** is currently on leave and will be available on **2026-07-07**.
Your query will be addressed upon their return. We appreciate your patience and understanding.
Best regards,
TI E2E Support Team
---
*This is an automated notification.*