search

quic-yocto / meta-qcom-hwe

MIT License
9 stars 22 forks source link

Please move bootloaders to a subdir #74

Open lumag opened 2 weeks ago

lumag commented 2 weeks ago

Having bootloader binaries just under ${DEPLOYDIR} unnecessary pollutes the directory and disallows multi-machine configurations. Please move bootloader binaries under board-specific dir under ${DEPLOYDIR}.

ndechesne commented 2 weeks ago

I think get your point.. let me add some details 1) to make sure I really understand what you meant, 2) to make sure it's clear to whoever will read that thread.

Currently in the IMG_DEPLOY folder we publish the following artifacts:

  1. the rootfs and image related files
  2. the DTBs generated during the kernel build (and dtb bin)
  3. the systemd boot artifact
  4. the boot binaries (from firmware-qcom-boot-qcs6490 recipe)
  5. the partitions files generated from ptool (a bunch of XML and others)

As of now, we only support single MACHINE configuration, e.g. 1 MACHINE per board. As such, when we publish artifact in DEPLOYDIR, they end up in tmp/deploy/images/${MACHINE} which is 'unique' per machine.

What you suggest is that we may (eventually) define 'generic' machines that are intended to build Yocto images which boot on more than 1 board (such as https://github.com/Linaro/meta-qcom/blob/master/conf/machine/qcom-armv8a.conf). In which case we would include more than 1 firmware 'artifact' and they would collide in DEPLOYDIR.

Is that what this issue is about?

lumag commented 2 weeks ago

Yes. E.g. I'm building recipes from your layer using the generic qcom-armv8a`. Having point 4 and 5 in subdir would definitely be more future-proof.