firmware-qcom-boot-common: provide virtual/bootbins #72
Conversation
Define a common virtual provider for bootbins, as we will later have multiple recipes providing boot binaries (based on base boards / SoCs). This is to help creating generic dependencies to the boot firmware recipe. Signed-off-by: Ricardo Salveti <[email protected]>
ricardosalveti
requested review from
quic-vkraleti and
sbanerjee-quic
as code owners
|
the name for the virtual provide is too generic, if we define a new provider, it should be at least with a qcom namespace. how about we wait until we really need this new provider? For now we are setting the dependency in the machine conf file, so we don't need the virtual provider. or am i missing something? |
Yup, I was looking at some of the hooks we use in meta-partner / meta-qcom-hwe and noticed the virtual was missing, but I agree we can hold this up until there is an actual need and user for it. |
Define a common virtual provider for bootbins, as we will later have multiple recipes providing boot binaries (based on base boards / SoCs).
This is to help creating generic dependencies to the boot firmware recipe.