[meta-xilinx] Provider of pmu-firmware [rel-v2018.1]

[Martin Siegumfeldt]

Hi,

Based on https://github.com/Xilinx/meta-xilinx-tools/commit/a516c3a4a8b29e07233b5f2ecf91a2a3e63a1ff7 I would like to switch from building the pmu-firmware using the XSDK (i.e. through meta-xilinx-tools) to the generated toolchain (i.e. through meta-xilinx). However the latter layer seems not (directly at least) to provide this:

martin at dell:~/work/tmp/xilinx$ ack ^'PROVIDES = "virtual/pmu-firmware' meta-xilinx-tools/ meta-xilinx
meta-xilinx-tools/recipes-bsp/pmu-firmware/pmu-firmware_git.bb
3:PROVIDES = "virtual/pmu-firmware"

Inspecting https://github.com/Xilinx/meta-xilinx/blob/rel-v2018.1/meta-xilinx-bsp/recipes-bsp/pmu-firmware/pmu-firmware_2017.3.bb

provides the following information:

# force this recipe to provide a target virtual/pmu-firmware. this is applied
# after any class extender mapping and results in this recipe always providing
# 'virtual/pmu-firmware'.
python append_target_provides () {
    d.appendVar("PROVIDES", " virtual/pmu-firmware")
}

which is not exactly clear to me? In any case, the recipes are named the same and I don't see how to switch between the providers? I tried deleting 'meta-xilinx-tools/recipes-bsp/pmu-firmware/pmu-firmware_git.bb' after which the meta-xilinx variant seems to be built but does not boot.

Am I missing something or is the provider concept broken/incomplete?

Br,
Martin