The module media and other modules are reusable for other modules, the package
should expose symbols to other packages.
The module.bbclass expects kernel-module- prefix package name and matching
include directory to trigger the dependency mechanism.
python __anonymous () {
depends = d.getVar('DEPENDS')
extra_symbols = []
for dep in depends.split():
if dep.startswith("kernel-module-"):
extra_symbols.append("${STAGING_INCDIR}/" + dep + "/Module.symvers")
d.setVar('KBUILD_EXTRA_SYMBOLS', " ".join(extra_symbols))
}
Add:
1. kernel-module-nvidia-kernel-oot PROVIDES alias.
2. Symlink of /usr/include/kernel-module-nvidia-kernel-oot -> /usr/include/nvidia-kernel-oot
A module that requires these modules can use the standard dependency such as:
DEPENDS += "kernel-module-nvidia-kernel-oot"
Signed-off-by: Alon Bar-Lev <alon.barlev@gmail.com>
Warnings are treated as errors and this warning is triggered when
compiling git version of nvidia-kernel-oot module. Ignore the
warning as error for now.
Fixes errors like
nvidia-oot/drivers/net/wireless/realtek/rtl8852ce/phl/hal_g6/phy/rf/halrf_8852c/../halrf_8852c/halrf_ops_rtl8852c.h:25: error: header guard '__HALRF_OPS_RTL8852C_H__' followed by '#define' of a different macro [-Werror=header-guard]
Signed-off-by: Khem Raj <raj.khem@gmail.com>
* pass -std=gnu17 and disable errors for unterminated string
initialization warnings in the test programs
* update the sed filter to catch -ffile-prefix-map for the
TA development kit
Signed-off-by: Matt Madison <matt@madison.systems>
The default prefix map settings have switched to using -ffile-prefix-map,
but the gcc 10 compiler we're building here needs the old -fmacro-prefix-map
and -fdebug-prefix-map settings, so add them back in for these recipes.
Signed-off-by: Matt Madison <matt@madison.systems>
This version emits a different internal name so it passes a check
added to egl-gbm at version 1.1.1. This does not alter functionality
in any way.
Signed-off-by: Kurt Kiefer <kekiefer@gmail.com>
With [1] the image_types_tegra class was modifed to add
the minimal uefi image, uefi_jetson_minimal, to the tegraflash
package and added edk2-firmware-tegra-minimal:do_deploy
to the do_image_tegraflash_tar[depends]
Since tegra-uefi-capsules also references tegraflash_populate_package
it also needs the same dependency to avoid this build error:
```
| DEBUG: Executing shell function do_compile
| cp: cannot stat '/home/dan/trellis/oe4t/tegra-demo-distro/build-r36.4.3/tmp/deploy/images/jetson-orin-nano-devkit-nvme/uefi_jetson_minimal.bin': No such file or directory
| WARNING: exit code 1 from a shell command.
```
1: 9b6a113255
Signed-off-by: Dan Walkes <danwalkes@trellis-logic.com>
to move the common parts for the two recipes into a shared include
file.
Also add the rtl8852ce driver to the wifi drivers list.
Signed-off-by: Matt Madison <matt@madison.systems>
* Update nvidia-container-toolkit, libnvidia-container to v1.16.2
* Refresh nvidia-container-toolkit alt-roots patch
* Drop obsolete backported patch and config.toml template file
* Use nvidia-modprobe patch in the libnvidia-container sources
instead of maintaining our own copy
* Other minor cleanup of obsolete settings in libnvidia-container
recipe
* Fix PACKAGE_ARCH of libnvidia-container for tegra platforms
* Add missing BSD-3-Clause license to nvidia-container-toolkit recipe
* Update license checksums in nvidia-container-toolkit recipe;
no license-affecting changes.
Signed-off-by: Matt Madison <matt@madison.systems>
When device-tree builds moved to nvidia-kernel-oot, the dtb files built from
the platform dts files were getting stashed into the sysroot area for future
use during image build, but the dts files themselves were *not* saved anywhere.
This broke external device-tree recipes that wanted to include the platform dts
and add modifications.
Add export of dts files into nvidia-kernel-oot sysroot area,
under usr/src/device-tree subdir.
Signed-off-by: S. Lockwood-Childs <sjl@vctlabs.com>
- 'mv generate_bup_payload.sh doflash.sh' should be
conditional on TEGRA_SIGNING_EXCLUDE_TOOLS. Those who
use external signing servers will set this to "1" which
skips the generation of generate_bup_payload.sh. See
invocations of tegraflash_generate_bupgen_script in
image_types_tegra.bbclass.
Signed-off-by: Chad McQuillen <chad.mcquillen@lexmark.com>
nvcc needs the cicc binary provided in the cuda-nvvm package, so
make sure that gets installed with the host-side SDK tools.
Signed-off-by: Matt Madison <matt@madison.systems>
zstd is a lot faster when compressing and decompressing, which helps
with iteration speed.
Use the CONVERSIONTYPES machinery builtin rather than re-implementing it
ourselves here.
Signed-off-by: Austin Schuh <austin.linux@gmail.com>
Signed-off-by: Matt Madison <matt@madison.systems>
OE-Core master has udpated how the toolchain virtual providers
are handled, so update the layer accordingly.
This affects the gcc-for-nvcc extra toolchain build we have for
CUDA builds, and a few other recipes that have some explicit
references to the old toolchain virtual/<something> names.
Signed-off-by: Matt Madison <matt@madison.systems>
USB instances might not be consistent between the Jetson boot ROM
and the mass storage USB gadget in the running OS, so make the
cross-check of the instance ID optional, and off by default.
This means that when flashing secureboot-enabled devices using
pre-signed binaries, only one target can be flashed at a time
from a given host.
Signed-off-by: Matt Madison <matt@madison.systems>
* Drop OpenSSL 3 support patch now included upstream
* Rework OE build integration to be a bit cleaner
* Update to use BBCLASSEXTEND for native, instead of
having a direct -native recipe
Signed-off-by: Matt Madison <matt@madison.systems>
Fix the change introduced in ff0795338b
to use a relative path, rather than an absolute path, so the full
build path doesn't get embedded in any of OP-TEE packages.
Signed-off-by: Matt Madison <matt@madison.systems>
Since we can't get the target's serial number out of the CVM EEPROM when
using pre-signed binaries, look for the USB instance in the device path
as a way of cross-checking that a storage device matches the target we're
trying to flash.
Signed-off-by: Matt Madison <matt@madison.systems>
