mirror of
https://git.yoctoproject.org/poky
synced 2026-04-16 15:32:13 +02:00
78e1856f58867c8a6ba2f40eb87c222cb81a1d07
If kdump.service is set to run on boot and dump-capture kernel isn't placed in /dev/root, kdump.service will fail to load the kernel, since other partitions are not mounted yet. Starting kdump.service after basic.target guarantees dump-capture kernel can be loaded in this situation. (From OE-Core rev: ac9a54fc617ff5f1eb75fa8500187c5ed3effe46) (From OE-Core rev: d6f922ddc14e0b17af5f1de46ec905de2a21a751) Signed-off-by: Yongxin Liu <yongxin.liu@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
oeqa/selftest/systemd_boot: Never use cleansstate in QA tests without special handling of SSTATE_DIR
QEMU Emulation Targets ====================== To simplify development, the build system supports building images to work with the QEMU emulator in system emulation mode. Several architectures are currently supported in 32 and 64 bit variants: * ARM (qemuarm + qemuarm64) * x86 (qemux86 + qemux86-64) * PowerPC (qemuppc only) * MIPS (qemumips + qemumips64) Use of the QEMU images is covered in the Yocto Project Reference Manual. The appropriate MACHINE variable value corresponding to the target is given in brackets.
Description