| Age | Commit message (Collapse) | Author |
|---|
|
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>
|
|
The do_qcom_img_deploy function references several variables (and flags)
in a way that is not visible to bitbake. Declare vardeps manually to let
bitbake know it and reschedule the function if one of variables changes.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
|
|
Follow recent OE-core changes and include ${IMAGE_NAME_SUFFIX} into the
initrd image name.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
|
|
Currently linux-qcom-bootimg.inc issues warnings like the following with
some versions of Python 3:
WARNING: linux-linaro-qcomlt-6.0-r0 do_qcom_img_deploy:
.../meta-qcom/recipes-kernel/linux/linux-qcom-bootimg.inc:51:
SyntaxWarning: "is" with a literal. Did you mean "=="?
Using is to test for equality is wrong. is only works "by accident" and
relies on some rather dubious assumptions about how CPython manages the
string literal pool
There are three occurrences, the first two are fixed the obvious way and
the final one is simply removed because the code was unreachable anyway
(the empty string already evaluates to False when used in a logic
expression).
Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
|
|
We do not need kernel images in the rootfs when using
linux-qcom-bootimg, the image is flashed into special partition instead.
So, prevent clobbering rootfs (and especially initramfs) with the kernel
images.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
|
|
Add support for bundling initramfs into android boot images. For example
this allows one to build bootable images containing the kernel and all
built modules/firmware to test them without flasing actual images to the
device.
To create kernel+initramfs bundles, just define INITRAMFS_IMAGE.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
|
|
Handle the creation of multiple Android boot images: set parameters like
rootfs device, boot address and page size based on KERNEL_DEVICETREE.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
|
|
Move machine-specific KERNEL_CMDLINE append to machine (db845c) config
file. Include file should not contain machine-specific settings.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
|
|
Basing on the kernel from kernel-devicetree.bbclass support several
devicetree files per machine. The first one from ${KERNEL_DEVICETREE} is
used for 'default' boot images.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
|
|
WiFi on RB5 requires all 32 MSI vectors, so don't let PCIe port steal
some of them from us. Pass 'pcie_pme=nomsi' to the kernel on RB5.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
|
|
In preparation to allowing rootfs specifications other than just a
device node, move '/dev/' prefix from linux-qcom-bootimg.inc to
individual machine config files.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
|
|
Some shells expect a whitespace before closing ']', so add one here,
fixing a syntax error. Also fix another syntax issue: use '=' instead of
'==' for comparing strings.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
|
|
We used to support DT table in the boot image (aka DT_BUNDLE), but
this is no longer used on any current platform. Let's remove the
support.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
|
|
Without this kernel variables in cmdline the a6xx gpu fails to
probe/init use it for now.
Signed-off-by: Aníbal Limón <anibal.limon@linaro.org>
(cherry picked from commit b1b280c6edee053761a8166e6bba4cd1cd2320ed)
|
|
Recently that variables was renamed,
http://git.openembedded.org/openembedded-core/commit/?id=f952c8e08b4798aa0f8bf764cfd70bda0eae9b8b
Signed-off-by: Aníbal Limón <anibal.limon@linaro.org>
|
|
|
|
Avoid installing skales tools in $bindir, mostly because mkbootimg conflicts
with mkbootimg from android-tools package.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
(cherry picked from commit da63ca630845558e3e350bbf9ffb3de3091a4972)
|
|
Since the last upgrade of skales recipes, it now loads libfdt.so directly (from
python using ctypes), so we need to set LD_LIBRARY_PATH so that it will find the
library in the relevant sysroot.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
|
|
into a single do_deploy_append for all targets, and move
the machine-/SoC-specific bootimg creation settings into
the relevant configuration files.
Signed-off-by: Matt Madison <matt@madison.systems>
[nicolas.dechesne@linaro.org: move dt image symlink creation]
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
|
|
and KERNEL_IMAGE_SYMLINK_NAME as the base for the
deployed dt and boot image names, to reduce redundancy.
Signed-off-by: Matt Madison <matt@madison.systems>
|
|
for appending to DEPENDS, since normal += will work in
this context.
Signed-off-by: Matt Madison <matt@madison.systems>
|
|
to the common include file that uses it, to reduce
duplication of code.
Signed-off-by: Matt Madison <matt@madison.systems>
|
|
For the kernel, we intend to use the same config and boot methods on all arm64
based devices. So instead of using apq8016 overrides, let's use the more generic
aarch64 overrides.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
|
|
In many recipes we have been using $MACHINE to add customization. As we are
about to add more boards based on similar SoC, we need to use $SOC_FAMILY as
override instead of $MACHINE.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
|
|
BOOT_IMG_NAME and DT_IMG_NAME were designed to mimic KERNEL_IMAGE_BASE_NAME, but
for some reasons their initial name was different.. let's align the name to
match the original variable.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
|
|
The kernel recipe gets rebuilt each time, because we use DATETIME in the output
name, let's fix that, and exclude DATETIME value from the dependency signature.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
|
|
fix typo..
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
|
|
To ease the deployment on the target, build a valid boot image that can be
booted with 'fastboot boot <image>', or flashed into the eMMC with 'fastboot
flash boot <image>'.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
|
|
as of now, the support for boot image is missing in IFC6410 bootloader, so let's
not create the boot image. We can revisit later when proper support is
implemented in the bootloader.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
|
|
Ouch, boot image won't boot because of the typo...
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
|
|
Add support for building the custom boot.img that can be booted on targets
running LK/fastboot. It takes care of the dt image creation as well, which needs
to be appended to the boot image.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
|
Dmitry Baryshkov
Daniel Thompson
Nicolas Dechesne
Aníbal Limón
Artur Mądrzak
Matt Madison