* Added patch to support location of files in the container-passthrough tree
* Added systemd service to generate the config.toml file for the container
runtime during boot, so we can add the location of the passthrough tree.
Signed-off-by: Ilies CHERGUI <ichergui@nvidia.com>
Signed-off-by: Matt Madison <matt@madison.systems>
* Dropped libnvidia-container-jetson recipe, which is now obsoloete
Signed-off-by: Ilies CHERGUI <ichergui@nvidia.com>
Signed-off-by: Matt Madison <matt@madison.systems>
tegra-flash-helper:
- DCE overlay DTB handling
- secondary_gpt_backup has been dropped
- EEPROM custinfo command changed to 'try_custinfo'
- PVA firmware
- remove SCE firmware
- drop odmsign.func check, as it is now included in the BSP
- add readfuses command on initial contact with device
- fix handling of custinfo data
- set up FLASHARGS variable for processing by odmsign
initrd-flash:
- now using module serial number/asset ID instead of ECID for
the unique identifier
- normal helper/tegraflash invocation can now generate
a signed RCM boot blob, so remove special hack for that
- reorder helper invocations in signing steps - RCM first,
then internal, then external
rewrite-tegraflash-args:
- updated from latest tegraflash.py script
Signed-off-by: Matt Madison <matt@madison.systems>
* Handle some changes to NVIDIA's build configurator, and
some path changes for scripts within the edk2-nvidia repo
* Move the rootfs A/B overlay to a separate recipe, so
it can also be used with prebuilt UEFI
Signed-off-by: Matt Madison <matt@madison.systems>
Drivers that are generally always needed are included in the
MACHINE_ESSENTIAL_EXTRA_* variables, so just include these in the
initrd-flash image.
Signed-off-by: Matt Madison <matt@madison.systems>
* More drivers are now kernel modules
* Switch from ECID to module serial number for
forming USB device ID when flashing
Signed-off-by: Matt Madison <matt@madison.systems>
This reverts commit 1eec81c883.
With L4T R36.x, we now have a 5.15 kernel as a base, so we no
longer need to do this.
Signed-off-by: Matt Madison <matt@madison.systems>
to build all of the NVIDIA out-of-tree modules and device trees.
This also removes the old nvidia-display-driver recipe, since the
source for the display drivers is coupled with the other out-of-tree
drivers.
Added patches for fixing:
* driver ordering between nvidia-drm and tegra-drm
* build compatibility with gcc 14
Signed-off-by: Matt Madison <matt@madison.systems>
- base OP-TEE version now 3.22
- refresh makefile patch
- optee-client now needs pkg-config and depends on libuuid
Signed-off-by: Matt Madison <matt@madison.systems>
The 'public' subdirectory has been removed. Also bump ATF version
to 2.8, which is the version included with L4T R36.3.0.
Signed-off-by: Matt Madison <matt@madison.systems>
The collection of dtb overlays used during tegraflash package creation
can come from sources other than l4t or the kernel. Most commonly this
is the virtual/dtb package, but it can be overridden, and is specified
by the DTB_EXTRA_DEPS variable.
The migration from creating bup payloads to creating only capsules
inadvertantly dropped this dependency, so this change adds it back.
Signed-off-by: Kurt Kiefer <kekiefer@gmail.com>
Drop bup-payload image type from TEGRA_INITRAMFS_FSTYPES, as it's
planned to generate BUP image inside UEFI capsule generation
recipes.
Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io>
Rename variable holding Capsule install dir in the final rootfs,
so it's more generic TEGRA_UEFI_CAPSULE_INSTALL_DIR and set
a weak default value, so it can be adjusted if needed.
Signed-off-by: Igor Opaniuk <igor.opaniuk@foundries.io>
There is now a check that ${S} exists after running do_unpack.
The convention for recipes with only local in-tree files is
to define S and point UNPACKDIR at the same directory. All
such recipes are updated to use this convention.
Signed-off-by: Matt Madison <matt@madison.systems>
There is now a check that ${S} exists after running do_unpack, so
append the extraction of the sources from the debian package to
the do_unpack task, instead of breaking it out as a separate
task.
Signed-off-by: Matt Madison <matt@madison.systems>
gcc 14 has promoted the int-conversion warning to the default -Werror
list, so update CFLAGS to prevent the error.
Signed-off-by: Matt Madison <matt@madison.systems>
Like the upstream gcc recipes, we can use the global DEBUG_PREFIX_MAP
setting, but for this older compiler we have to remove '-fcanon-prefix-map'.
Signed-off-by: Matt Madison <matt@madison.systems>
The function-finding compilation tests were getting a false positive because gcc 14
promoted the implicit-function-declaration warning to the -Werror defaults. Work
around this by disabling this error in the CC setting we pass to make.
Signed-off-by: Matt Madison <matt@madison.systems>
* No more 'S = "${WORKDIR}"', which is not permitted
* All ${WORKDIR} references for local files updated to ${UNPACKDIR}
* Custom do_unpack for the recipes that are in the public_sources
archive in the BSP adjusted for the new unpacking approach
* Some SRC_URIs updated with 'destsuffix=' parameters where needed
Signed-off-by: Matt Madison <matt@madison.systems>
The original problem with compatibility with newer version of libtirpc was
resolved, so we don't need the workaround any longer.
Also drop runtime dependencies that have been moved to the main libnvidia-container
recipe. This package can't be used on its own, anyway, as it's called on
by the nvidia-container-cli tool built in the libnvidia-container recipe.
Signed-off-by: Matt Madison <matt@madison.systems>
* Refresh the build patch to have nvcgo built, so the library can be used
with cgroupsv2 (for 'auto' and 'csv' modes)
* Move some runtime dependencies from libnvidia-container-jetson to
this recipe, as they're needed here
* Patch the toolkit to implement 'alternate roots' for locating files to be
passed through from the host, to support our tegra-container-passthrough tree
* Provide our own config file, rather than modifying the one from the source tree
on the fly
This enables us to support 'csv' mode in the toolkit for our builds, instead
of requring 'legacy' mode. With 'csv' mode, host passthrough mounts are injected
into the container when it is created, rather than using the legacy method of
adding a prestart hook to run nvidia-container-cli to set them up.
The 'legacy' mode can still be used, if needed, as long as your target system
is configured to support cgroupsv1.
Signed-off-by: Matt Madison <matt@madison.systems>
Previously the 17 standard was needed just for some plugins, and leaving
14 was fine for the rest of the project. With recent changes to absl, now
we need the 17 standard for other parts as well.
This change builds on the do_configure:prepend sed fixup to include the
CMakeLists.txt CMAKE_CXX_STANDARD being forced in a couple more places.
Signed-off-by: Kurt Kiefer <kekiefer@gmail.com>
This makes it possible for extra custom steps to take before the final reboot step of the initrd flashing process.
A new recipe can use the TEGRA_INITRD_FLASH_INSTALL variable in the distro config, to add the new package(s) that provides the custom extra init steps.
Note that these scripts needs to be installed with execution permition, in the /init_extra.d folder of the tegraflash initrd image.
Signed-off-by: Michael Christensen <msc95@hotmail.dk>
