Is there a timeline for updating yocto repo manifest for latest yocto and Linux kernel?

Technical Support
, ,
1

Hi,

I am currently building images based on tdx-reference-minimal-image for a verdin-imx8mp and custom carrier board.

I know there is still a while before kirkstone is EOL.
But I am working on a project that ideally needs the updated drivers in Linux 6.x and not the current 5.15.
Also there are several other recipes that we would ideally like to use newer versions of.

I have seen that there is a Scarthgap branch and was wondering if that is at all in a working state / supported yet?

2

Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

As of now, the Scarthgap branch is an experimental branch and not officially supported for production use. It is intended for early testing and development purposes. The timeline for updating the official Toradex Yocto Project layers and repo manifests to support the latest Yocto and Linux kernel versions, such as Linux 6.x, has not been officially announced.

For your project needs, you can try using the Scarthgap branch, but be aware that it may not be stable and could require additional adjustments and testing on your part. If you need the updated drivers and newer recipe versions urgently, you might consider manually integrating the necessary updates into your current setup, though this can be complex and time-consuming.

For the most accurate and up-to-date information, I recommend keeping an eye on the Toradex developer website and forums, or reaching out directly to Toradex support for any specific timelines or updates regarding the official support for newer Yocto and Linux kernel versions.

1 Like
3

Hi @izzycoding ,

Our Scarthgap based BSP will be version 7.X and indeed you are correct we have started working on it. Rough timeline for it to be available may be late October or November.
Would that timeline work for you?

And to answer your questions yes early work seems very promising but of course it needs to be put through its paces and validated well.

Best regards,

4

Hi @michael.tx

That sounds great.
Sadly that is not good for our current release (which is middle of next week).
However, it will be fine for our next release, so I may start working on the new branch once this release is over so we can be ready out the gate for our first update.

Then the next step is looking at using a custom Torizon build.

5

Thank you for letting us know.

However, it will be fine for our next release, so I may start working on the new branch once this

Out of curiosity, when approximately is your next released planned for? Also how often do you do new software releases? It sounds somewhat frequent/regular.

Best Regards,
Jeremias

6

Hi @jeremias.tx,

Our current plans are to have updates 3-4 times a year (ideally just after the releases you do).

However, the likelihood of that happening for our first batch is probably more like yearly, due to how we have had to integrate things for some of our requirements (basically the first major update will likely require a new SoM, unless there is a way to provide a signed tezi image in our spare partition).

Also, there are quite a few hardware changes we want to make for our second version, so it may be a case of swapping v1 for those when we have it all sorted rather than the rush to the deadline we have now.

7

Okay that’s good for us to know.

Do you have any further questions about our own software release structure? Or are you satisfied with what we’ve shared so far?

Best Regards,
Jeremias