OE4T Meeting Notes 2021 09 09

Video:

Unfortunately did not get recording again this month. Switching to Zoom next month.

11

See https://github.com/OE4T/meta-tegra/discussions/776 for test sheet.
Automated testing for multimedia API and VPI samples new this month, updates reflected in the test sheet.
Still no testing of non-passthrough support for docker containers. Need to go back through NVIDIA presentation at https://info.nvidia.com/jetpack-deep-dive-reg-page.html, find containers which use partial passthrough, and include these in the test matrix to verify this is also supported on meta-tegra and Yocto.

See https://github.com/oe4t/meta-tegra/discussions/784 ** Bug in v4l2 component delivered in binary form, calling pthread_join with null thread ID and undefined behavior. ** Not noticed in debian distros due to a patch in glibc which hasn’t made it upstream. ** Added a wrapper from nvvidconv plugin in https://github.com/OE4T/meta-tegra/issues/785 which prevents duplicate STREAMOFF. ** Have a script which automates the process of testing samples on all platforms, tested with 32.4.3, 32.5 and 32.6. Needed in all places. ** Would be nice to get a fix from NVIDIA for this, could be an easy fix, would eliminate the need to maintain the wrapper.

Don’t plan to backport any additional changes unless there are lots of demand. General consensus is to avoid making major changes on existing branches.

Questions about tooling and offline signing. Ran into a chip with a FAB value that’s not in NVIDIA tooling. ** Opened a post on the developer forum about new FAB value not in L4T kit.
Potentially some risk supporting an unsupported FAB with signing. Approach taken for production on TX2 is to just use flashing to get installer image onto device. Have the installer program in the correct set of bootloader binaries. Make sure when it comes off the factory line it has the right set for the particular SOM, attributes, FAB rev. Installer has minimal set of dependencies, may not be exactly right but enough to get the right signing tools for FAB installed.

See https://github.com/OE4T/meta-tegra/discussions/793 ** Hesitant to use TensorRT sources, difficult to align jetpack releases with tags in open source repository. ** Doable with TensorRT 8, might be possible to build from source. ** Based on build time option the tensor RT wouldn’t install plugins, would RDEPEND on recipe that provides from source. ** Might want to put an option to pull in specfic tensorrt source built plugins in meta tegra if we can make general enough. Didn’t see dependencies which would be difficult to put into the layer.

Will likely have bigger problems trying to run containers with passthrough mechanism on future openembedded branches after honister which updates glibc version, based on discussions in openembedded mailing list.

Some registers are protected from reading. There’s a security configuration register loaded at boot time which puts some registers inside trusted. Only readable from trusty.

Please note - moving to Zoom for future meetings to resolve issues with recordings