Kurt Kiefer 411b175fd4 nvidia-kernel-oot: deploy virtual/dtb in separate recipe ...

Custom boards wishing to provide their own devicetree sources will
want to be a provider of virtual/dtb. If this happens, then other
providers of virtual/dtb will not be built. That's a problem, because
the nvidia-kernel-oot recipe also contains device drivers and overlay
devicetree sources that are required.

To solve this, the deployment step of nvidia-kernel-oot is broken
out into a special provider for virtual/dtb. That way, it can easily
be skipped by creating a new virtual/dtb provider and the rest of
nvidia-kernel-oot can still be built and used.

Signed-off-by: Kurt Kiefer <kekiefer@gmail.com>

2024-07-12 03:03:29 -07:00

..

machine

nvidia-kernel-oot: deploy virtual/dtb in separate recipe

2024-07-12 03:03:29 -07:00

layer.conf

layer.conf: prune SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS

2024-05-31 09:57:00 -07:00