Closed roby2014 closed 8 months ago
It looks like you've added patches to the kernel recipe for your TX2-based builds. Those patches won't apply to the 5.10 kernel in L4T R35 and later. You really can't mix TX2 and Orin in the same builds - the NVIDIA BSPs are completely different. That's why we have separate kirkstone branches for the two.
Thanks for the information. Whats the proper solution for this? How can I remove/add that package for my specific board?
I build with kas
so I could add something like IMAGE_INSTALL:append = "gstreamer1.0-omx-tegra"
to tx2.yml
and `IMAGE_INSTALL:remove += "gstreamer1.0-omx-tegra"?
That sounds like you're asking about #1521 that you raised... I don't really know much about kas, but you need to track down where that package is getting pulled in. If you've added it directly in your image recipe, then what you propose might work. It's also possible, though, that it's getting pulled in as a runtime dependency for some other package you're building, in which case you need to fix that package so it no longer has that dependency. That could be more than just a recipe modification - code may have to be changed.
Similarly for the patch problem you mention here - track down where those patches are being added, and fix your recipes/bbappends/kas settings/etc. so that they apply only to the builds for your TX2-based machine. The specifics of how to do that really depend on how you've got your build environment set up.
I putted COMPATIBLE_MACHINE="jetson-tx2-devkit"
on linux-tegra_%.bbappend
which does kernel mods for tx2. However if I compile for orin, I get:
ERROR: Nothing PROVIDES 'virtual/kernel'
linux-yocto-rt PROVIDES virtual/kernel but was skipped: incompatible with machine p3768-0000-p3767-0001 (not in COMPATIBLE_MACHINE)
linux-yocto-dev PROVIDES virtual/kernel but was skipped: incompatible with machine p3768-0000-p3767-0001 (not in COMPATIBLE_MACHINE)
linux-yocto-tiny PROVIDES virtual/kernel but was skipped: incompatible with machine p3768-0000-p3767-0001 (not in COMPATIBLE_MACHINE)
linux-dummy PROVIDES virtual/kernel but was skipped: PREFERRED_PROVIDER_virtual/kernel set to linux-tegra, not linux-dummy
linux-yocto PROVIDES virtual/kernel but was skipped: incompatible with machine p3768-0000-p3767-0001 (not in COMPATIBLE_MACHINE)
linux-yocto-custom PROVIDES virtual/kernel but was skipped: incompatible with machine p3768-0000-p3767-0001 (not in COMPATIBLE_MACHINE)
linux-yocto-tiny PROVIDES virtual/kernel but was skipped: incompatible with machine p3768-0000-p3767-0001 (not in COMPATIBLE_MACHINE)
linux-yocto-rt PROVIDES virtual/kernel but was skipped: incompatible with machine p3768-0000-p3767-0001 (not in COMPATIBLE_MACHINE)
linux-yocto-upstream PROVIDES virtual/kernel but was skipped: incompatible with machine p3768-0000-p3767-0001 (not in COMPATIBLE_MACHINE)
linux-yocto PROVIDES virtual/kernel but was skipped: incompatible with machine p3768-0000-p3767-0001 (not in COMPATIBLE_MACHINE)
linux-tegra PROVIDES virtual/kernel but was skipped: incompatible with machine p3768-0000-p3767-0001 (not in COMPATIBLE_MACHINE)
ERROR: Required build target 'myos-image' has no buildable providers.
Missing or unbuildable dependency chain was: ['my-os', 'virtual/kernel']
any suggestion for this?
Try renaming the bbappend to include the version number, e.g. linux-tegra_4.9%.bbappend
Thank you, fixed by adding:
BBMASK += "/meta-tegra-tek/recipes-kernel/linux/linux-tegra_4.9.bbappend"
PREFERRED_PROVIDER_virtual/kernel = "linux-tegra"
PREFERRED_VERSION_virtual/kernel = "5.10"
Trying to build
p3768-0000-p3767-0001
, branchkirkstone
. I get the following: