Jetson Xavier AGX in Scarthgap or newer

[elbbit01]

Hi guys,
I am long working in a project for nvidia jetson Xavier AGX based on the kirkstone branch.
We have to update the yocto layers because of other dependencies, but I see there is not support for jetson linux R35.X any more, and jetson linux R36.X is not supporting officially Xavier AGX.

Do you have some advise? Is it possible that anyway the R36.X would work on Xavier AGX? Would it be easier to take scarthgap and adapt manually everything to point to 35.X? I see that a huge effort but probably useful for a lot of people.

Thanks in advance,
Alvaro.

[elbbit01]

forget about it, I just found there is a subbranch for it.
The question stays for newer branches, though. How long can I use R35.X?
Is it expected to be supported on Walnascar for example?

[madisongh]

There are no plans to extend support for JetPack 5/L4T R35.x to newer branches past the scarthgap LTS base. I don't think NVIDIA has EOLed it yet, but if you look at their current roadmap page, you'll see it only mentions JetPack 6 and JetPack 7, so I would expect to see something soon. Even if we don't, if JetPack 4/L4T R32 history is anything to go by, I would only expect to see minimal fixes applied to it.

I think it would be technically possible, if maybe a bit painful, to bring the R35.x support up to newer branches, but there's the question of bandwidth/resources. If someone has the need to carry R35.x support beyond the scarthgap support timeframe (April 2028) and can commit resources to port it to master latest, and keep up with the newer branches, and continue that support through the next LTS window (which would probably be out to April 2030), that would be great. But with the small number of volunteers we have to maintain the layer, I have to limit the number of branches and versions we support.

[elbbit01]

Thanks a lot for the answer. It is as I thought.
I would like to help here but I am not sure what will be our decision about it and our possibility for a time/effort commitment.