classes/image_types_ostree.bbclass: add device tree to boot/devicetree-*

Include device trees into boot/devicetree-*-checksum. Device trees with
this name format get picked up by ostree and copied into boot/.
Ostree also generates entry inside uEnv.txt called fdt_file pointing to
this device tree.

Normaly one would include only one device tree. If KERNEL_DEVICETREE
includes more then one device tree this will add all the device trees
but ostree will still pick only one device tree and include it into
boot.

We are working on modifications to ostree so it will pickup all
the device trees.

Signed-off-by: Luka Pivk <luka.pivk@toradex.com>

1 files changed, 1 insertions, 0 deletions

diff --git a/README.adoc b/README.adoc
index 994ad67..ea9bb21 100644
--- a/README.adoc
+++ b/README.adoc
@@ -88,6 +88,7 @@ Although we have used U-Boot so far, other boot loaders can be configured work w
 * `SOTA_CLIENT_FEATURES` - extensions to aktualizr. The only valid options are `hsm` (to build with HSM support) and `secondary-network` (to set up a simulated 'in-vehicle' network with support for a primary node with a DHCP server and a secondary node with a DHCP client).
 * `SOTA_SECONDARY_CONFIG_DIR` - a directory containing JSON configuration files for virtual secondaries on the host. These will be installed into `/etc/sota/ecus` on the device and automatically provided to aktualizr.
 * `SOTA_HARDWARE_ID` - a custom hardware ID that will be written to the aktualizr config. Defaults to MACHINE if not set.
+* `OSTREE_DEPLOY_DEVICETREE` - Set this to '1' to include devicetree(s) to boot
 
 == Usage