OE4T Meeting Notes 2024‐08‐08 - OE4T/meta-tegra GitHub Wiki

Video

https://youtu.be/XUiuKLrgDZo

Attendees

7

Topics

  • r32.7 branch container passthrough fixes.
  • digsigserver changes are PRd, will publish new version with rockchip changes
  • Xavier port to Jetpack 6
    • See thread in element here
    • Motivations:
      • Product needs encoding support, not as good of encoding support available in Orin.
      • Will need to stay up to date long term for cybersecurity concerns for 5-10 years.
    • Only a handful of patches needed to get to Linux 6.6. Most patches already upstreamed in 6.6. Less than 10 packages needed to pull in.
    • Most drivers use the same hardware with Orin and Xavier. In other cases, the Xavier was just removed from the devicetree, this was the only change.
    • Started with R35, working to upgrade kernel, pulled in drivers needed from R36.
    • Now started with R36 and pulling pieces of R35 back in.
      • Started work in meta-tegra-community. Will send for review when available.
    • Working on custom AGX Xavier hardware. Haven’t tried on devkit
      • Don’t have HDMI, haven’t tried that.
      • Have displayport through USB-C but not using same alternate mode chip so not sure how that will work on devkit
      • VIC works for videoscaling, encoders and decoders work.
      • Qt working with GBM backend. EGL streams didn’t run right off.
    • Things which are missing and might not be possible:
      • SLDCC non CSI camera drivers
      • DSI panels, all devicetrees are not there anymore. Displaydriver changes for Orin
      • NVLink drivers are missing
    • Broken but probably fixable
      • nvpmodel - should be doable to get running but doesn’t work with r35 drivers.
    • Flash helper script and handling components removed
      • Could put back in to meta-tegra, might be strage since we don’t have support for machines there.
      • Pull into meta-tegra-community
      • Put machine specific changes in dedicated scripts which can be pulled in through meta-tegra-community.
      • Decision: would be fine to put flash support back into meta-tegra for machines which aren’t supported in the layer
    • Haven’t looked at secureboot.
    • Still using R35 for UEFI at the moment.
      • Some questions about what to do with UEFI long term, whether to attempt to update.
    • Display subsystem is totally changed, going from nvdis which combined serial output with graphics libraries. Now using out of tree tegra drm driver (not NVIDIA). Same as the one which was upstreamed. Trick was not to initialize hdmi and displayport on same outputs. This provides KMS. Should also provide console framebuffers. Would mean we could pass display framebuffer from UEFI to the kernel. Not sure about initializing displays in UEFI, haven’t looked at that. Orin is a proprietary blob which runs in firmware.
    • Based on upstream 6.6 but probably will also work with NVIDIA’s kernel. May be good to setup by default with NVIDIA’s kernel so the BYO kernel setup isn’t required.
  • BYO kernel
    • Build for out of tree drivers happens with NVIDIA custom scripts
    • Would like to avoid having recipes for other kernels in the meta-tegra layer.
    • Supporting the yocto kernel and upstreaming patches there might be one good option.
    • Try to keep the number of options limited and relatively up to date. Might be open to have one alternate recipe, maybe OK if it breaks.
    • Fine having hooks in place if we don’t have them already which allows operation with other kernel
    • As long as we focus on one kernel less concerned about which one it is. Supporting upstream yocto LTS might be an option. Still some concerns about new releases.
    • Master could always be focused on Yocto LTS, scarthgap could stay with nvidia upstream.
    • Plan to work to move master to Yocto LTS kernel, see how difficult it is to integrate new NVIDIA releases.
    • Think about when to migrate to branches, probably next LTS after scarthgap.
  • swupdate on master
    • See https://github.com/OE4T/tegra-demo-distro/pull/305
    • Missing the l4tloader update, still worked to update from kirkstone to master with latest implementation.
    • esp-alt partition on orins may be placeholder, may not be used.
    • Can only have one partition with UUID matching EKS used by UEFI
    • Can potentially switch eks partition, or swap GUIDs.
    • More work is necessary to come up with a solution for updating L4TLoader.
  • Mender now supported on kirkstone branch with Jetpack 5 - see https://github.com/mendersoftware/meta-mender-community/pull/394