To be ARM System Ready IR compliant, QCOM UEFI implementation is now
supporting loading a matching device-tree by reading 'combined-dtb.dtb'
from the dtb partition.
linux-qcom-dtbbin.bbclass when inherited by kernel recipe, generates one
vfat image per dtb by packing dtb as 'combined-dtb.dtb'. This image can
be flashed into dtb parititon for UEFI to read and load device-tree.
Signed-off-by: Viswanath Kraleti <quic_vkraleti@quicinc.com>
linux-qcom-uki recipe generates UKI by combining UEFI stub, kernel image,
initrd, os-release, optional dtb and other metadata like kernel cmdline.
Drop uki.bbclass as linux-qcom-uki is taking care of UKI generation.
Signed-off-by: Viswanath Kraleti <vkraleti@qti.qualcomm.com>
Oe-core's image-uefi.conf defined EFI_UKI_PATH to point to the uki
inside an esp image. Use this variable in place of EFILINUXDIR.
Also, renamed a few other EFI variables for readability.
Signed-off-by: Viswanath Kraleti <quic_vkraleti@quicinc.com>
KERNEL_DTBDEST is the right place to look for dtb files. This variable
may deafult to KERNEL_IMAGEDEST but not always. So to avoid failures
it is must to read dtb files only from KERNEL_DTBDEST.
Signed-off-by: Viswanath Kraleti <quic_vkraleti@quicinc.com>
A unified kernel image (UKI) can be booted directly from UEFI.
The UKI is composed by an UEFI stub, the kernel Image, initrd and
other metadata like kernel cmdline.
This bbclass upon inherting in kernel recipe, generates UKI and
places the same under DEPLOY_DIR_IMAGE.
Signed-off-by: Viswanath Kraleti <quic_vkraleti@quicinc.com>
In order to improve sharing of the bootimg code, convert it to the
BitBake class instead of it being just an include.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
On some Qualcomm platform, the firmware reside in their own partition, in such
situation we can mount this partition automatically at boot.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
