Ampere/aarch64 bring-up changes

* Refactor the efi-secure-boot feature (in order for it to be
disabled for certain targets)
* Add support for emag8180 compilation target (used as Enea NFV Access host)
* Add emag8180 support in ostree
* Add support for qemuarm64 compilation target (used as Enea NFV Access VNF)

Note:
The aarch64 family does not support the secure-boot feature yet, so the
"efi-secure-boot" has been disabled.

Change-Id: I32336761d322102a07d065c9ab02ea5051854609
Signed-off-by: Adrian Stratulat <adrian.stratulat@enea.com>

1 files changed, 11 insertions, 0 deletions

diff --git a/images/enea-nfv-access.bb b/images/enea-nfv-access.bb
index 9311992..845e668 100644
--- a/images/enea-nfv-access.bb
+++ b/images/enea-nfv-access.bb
@@ -1,7 +1,18 @@
 DESCRIPTION = "Image for the host side of the Enea NFV Access Platform with ODM and NETCONF Edgelink customizations"
 
+IMAGE_FSTYPES_append_aarch64 = " live"
+IMAGE_TYPES_MASKED_append_aarch64 = " hddimg iso"
+NOISO_aarch64 = "1"
+NOHDD_aarch64 = "0"
+
 require images/enea-nfv-access-host-common.inc
 
 IMAGE_INSTALL += " \
     element-vcpe \
     "
+
+# On AARCH64, the OVMF firmware images are required by KVM, but these images are not
+# pulled explicitly by other recipes.
+IMAGE_INSTALL_append_aarch64 = "\
+    ovmf \
+    "