qemu-xilinx-system-native: Move pmu-rom enablement to recipe

Setting the pmu-rom being required by QEMU within the machine.conf will cause
the recipe's hash to change, which can cause a ripple effect causing other
things to rebuild.  Moving this to the recipe, and switching it on based
on what licenses the user allows will avoid this conflict.

Additionally add a warning message to the xilinx-vars.bbclass if the user has
not enabled the license.

Signed-off-by: Mark Hatle <mark.hatle@amd.com>

1 files changed, 6 insertions, 0 deletions

diff --git a/meta-xilinx-core/classes/xilinx-vars.bbclass b/meta-xilinx-core/classes/xilinx-vars.bbclass
index a1a0e38c..51d3cd87 100644
--- a/meta-xilinx-core/classes/xilinx-vars.bbclass
+++ b/meta-xilinx-core/classes/xilinx-vars.bbclass
@@ -23,4 +23,10 @@ python xilinx_variables_config_eventhandler () {
         bb.fatal("The loaded DEFAULTTUNE is %s, but it appears you intended %s. " \
                  "This is usually as a result of specifying it after the 'require' in the machine .conf file. " \
                  "See meta-xilinx-core/conf/machine/README." % (tune_prior, tune_final))
+
+    # Verify 'xilinx' is in LICENSE_FLAGS_ACCEPTED
+    license_flags = d.getVar('LICENSE_FLAGS_ACCEPTED') or ""
+    if 'xilinx' not in license_flags.split():
+        bb.warn("The ZynqMP pmu-rom is not enabled, qemu may not be able to emulate a ZynqMP system without it. " \
+                "To enable this you must add 'xilinx' to the LICENSE_FLAGS_ACCEPTED to indicate you accept the software license.")
 }