See the question at topic.
If we create our own rootfs from generic Ubuntu base image, eg. “ubuntu-base-18.04.5-base-arm64.tar.gz”, is anything of Tegra or Jetson Nano affected or missing?
I compared Nvidia released Tegra_Linux_Sample-Root-Filesystem of R32.3.1, R32.4.3 and R32.4.4, there are many files different among version. Why sample rootfs has many differences for different version of L4T/JetPack SDK?
Is there a document describe how Nvidia generate Tegra_Linux_Sample-Root-Filesystem package?
Thanks, we know how to create our rootfs. The question in op is “If we create our own rootfs from generic Ubuntu base image, eg. “ubuntu-base-18.04.5-base-arm64.tar.gz”, is anything of Tegra or Jetson Nano affected or missing?”,
or as subject of this topic: “Does Tegra_Linux_Sample-Root-Filesystem_Rxx.y.z_aarch64.tbz2 have Nvidia’s own change for Tegra or Jetson Nano?”
is /usr/lib/aarch64-linux-gnu/ the only place that we need to check? any other config file in Tegra_Linux_Sample-Root-Filesystem_Rxx.y.z_aarch64.tbz2 we need pay attention to ?
there’re several library besides /usr/lib/aarch64-linux-gnu/, for example, /usr/lib/xorg/modules/drivers/nvidia_drv.so.
suggest you based-on Tegra_Linux_Sample-Root-Filesystem to have your customization.
thanks
can you share the script how Nvidia make the rootfs in each jetpack release ? as we noticed every jetpack release the rootfs system are different . as we are making our own rootfs system for prodution we are worried wihtout understanding how jetpack rootfs is made we might miss importand feature.
according to developer guide, Setting Up Your File System.
you may access L4T Sample Root File System for each L4T release from the download center for reference.
it is script file, apply_binaries.sh to copy the NVIDIA user space libraries into the target file system.
thanks