OE4T Meeting Notes 2025‐04‐10 - OE4T/meta-tegra GitHub Wiki

Attendees

7

Video

https://youtu.be/8UelsoxoBUU

Discussion

Meeting Time

  • Will update for next timeslot.

r36.4.3 PR status

  • See https://github.com/OE4T/meta-tegra/pull/1837
  • If doing the backport to scarthgap want to ensure we are stable with Jammy 5.15. Enough coverage across enough different orins.
  • Khem Tested orin AGX
  • 36.4.4 is likely imminent - updated out of tree modules repo with 36.4.4 branch.
  • Should we wait for scarthgap backport?
  • Wouldn’t require backport of out of tree kernel stuff.

Patches for out of tree modules

  • 6.12 working in master branch
  • Previously all patches to out of tree modules were in meta-tegra.
  • Matt MIrrored all of nvidias git repos into our github, setup as submoudles
  • Upgrading involves pulling from nvidia’s downstream to keep up to date
  • Patches on 6.12 aren’t in NVIDIAs repos yet, not a synch with them but patches on top.
  • What is the policy for patches which aren’t build related, aren’t coming from nvidia. Should we pollute out of tree repos? Should it go into a fork of the kernel or patches in meta-tegra?
  • We should have one place we keep patches… since we went to the trouble of creating the git repo we should put there.
  • Need two PRs, one to update the submodule and one to update the parent tree with submodules.
  • Git subtrees is another option, makes it more difficult to match up changes with upstream.
  • Alternative to submodules would be to put each one of the repos in the SRC_URI. This might work better with devtool. Used the submodules because attempting to use outside yocto, easier to use in that regard.
  • Started with NVIDIA’s rel-36 branch which were more compatible with later kernel versions, wasn’t an official release.
  • 6.12 wasn’t something they had worked with.
  • Comparing to the 36.4.4 branch which will be part of the next official release, will support at least 6.11. Are some differences in the drivers. Not sure how significant those are.
  • Anything we use which aren’t from nvidia might result in strange compatibility issues, we may be the first ones to use them. We may not know what we don’t know.
  • Nvidia is currently at 6.6 or 6.8
  • Might make sense to use 36.4.4 branch for 36.4.3

Walnascar Branch for new Yocto Release

  • Wait for 36.4.3 or do now and rebase.
  • Will try to merge 36.4.3 first, depending on status of 36.4.4 and upstream 6.12 kernel changes merge.

GCC 15 support

  • Change the C dialect to be c23. Lots of fallout.
  • Will have in the next release of yocto.
  • Can be mitigated by specifying the c dialect on the command line. Will use this where we can’t fix it. Where we can cleanup the code this is a better option.

Amsterdam ELC Europe

  • Tim proposing two presentations, both with NVIDIA
  • Labgrid
  • wisk and pyrex. Orin Nano and Orin AGX

Swupdate ESP partition Updates

Kas Demos