linux/poky.git/meta/conf/machine, branch yocto-2.4

arch-x86: Add x86-x32 to MACHINEOVERRIDES

2017-09-26T10:05:01+00:00

This is needed as an x32 more generic x32 override later in the OVERRIDES, currently linux-gnux32 is the first override, but we need a stronger (later in the list) x32 override to deal with some needed x32 dependency overrides. (From OE-Core rev: 364b3698b78e9fea59d24e3a3a5f4476be95f6d1) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

qemu conf: Fix kernel module autoloading for uvesafb on genericx86

2017-09-13T21:07:42+00:00

After commit e8b1c653946ef921b65d47e52aea0dc530ef4286, we started seeing errors like the following during boot on genericx86 machines: uvesafb: failed to execute /sbin/v86d uvesafb: probe of uvesafb.0 failed with error -22 uvesafb: vbe_init() failed with -22 uvesafb: Getting VBE info block failed (eax=0x4f00, err=-2) These were caused because the uvesa module was being loaded during boot, when it is only meant to be loaded on qemu according to: 6af89812e8a9931ffed63768ed85367519bf7aef Since genericx86-common.inc includes qemuboot-x86, the module also tries to be loaded on genericx86 machines, this patch removes the instruction from qemuboot-x86 and adds it in specific to both qemux86 machines confs so it is correctly loaded only on those. [YOCTO #11879] (From OE-Core rev: 261f9c382121c73b72556a151fdd4c7938b32a92) (From OE-Core rev: 554903483acb4af402feaba013366388db89e36b) Signed-off-by: Alejandro Hernandez Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

qemu: bump default version to 4.12

2017-08-23T11:06:51+00:00

Not all the qemu machines carry default kernel specifications. While we could drop these references, we'll bump them to 4.12 to pick up the latest and remove them in future commits. (From OE-Core rev: c58df63d88a07d3275e7337f7d284b0a50db82cc) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

qemu conf: replace deprecated option with new option

2017-08-19T21:15:39+00:00

Replace the deprecated '-usbdevice' option with '-device usb-xx' option. This would fix runqemu boot error like below. '-usbdevice' is deprecated, please use '-device usb-...' instead (From OE-Core rev: 2f1f3480d344f8521e01f456d2dcd6c4e989ec59) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

x86-base.inc: enable live image type

2017-08-09T08:24:16+00:00

live image type was replaced by hddimg recently. This made NOHDD and NOISO options ineffective as they only influence live builds. It also causes image building failure for image sizes >4Gb Returned back live image type and disabled building iso image. This doesn't change result (hddimg is built), but it makes NOHDD and NOISO working as expected. [YOCTO #11842] (From OE-Core rev: c787dcdd55bc55c6c64dec21b251706615114fe7) Signed-off-by: Ed Bartosh Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

qemux86 qemux86-64: Enable pci

2017-08-09T08:24:15+00:00

lspci and some other software require "pci" in MACHINE_FEATURES and PCI is valid in the qemux86* context. (From OE-Core rev: aec9a159dbc7a78953da73ba9dfccc9e9c9514a7) Signed-off-by: He Zhe Signed-off-by: Richard Purdie

x86-base: build only hddimg, rather than iso and hddimg, for x86 machines

2017-07-17T13:01:36+00:00

(From OE-Core rev: 1e05d488f9f09230d2f7cd3f43a385ad206066f8) Signed-off-by: Joshua Lock Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

v86d, qemuboot-x86.inc: use KERNEL_MODULE_AUTOLOAD+KERNEL_MODULE_PROBECONF for uvesafb instead of fbsetup init script

2017-06-28T19:55:08+00:00

* also add UVESA_MODE variable for easier change of resolution and respect it in QB_KERNEL_CMDLINE_APPEND as well * don't use init script just to call modprobe * I wasn't able to test this all the way with runqemu, because runqemu doesn't work on my system, but I've verified that the right params appear there and that I can easily change UVESA_MODE from conf/local.conf, the modules.d and modprobe.d files look OK: OE qemux86@ ~/build/oe-core/tmp-glibc/deploy/images/qemux86/core-image-sato-qemux86-20170427212613.rootfs $ cat etc/modules-load.d/uvesafb.conf uvesafb OE qemux86@ ~/build/oe-core/tmp-glibc/deploy/images/qemux86/core-image-sato-qemux86-20170427212613.rootfs $ cat etc/modprobe.d/uvesafb.conf options uvesafb mode_option=1600x1200-32 so I'll be able to drop this KERNEL_MODULE_AUTOLOAD + KERNEL_MODULE_PROBECONF from my DISTRO conf. (From OE-Core rev: f7ba5b5f76bb5678ca3e6ad51586f25871f7a9fb) Signed-off-by: Martin Jansa Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

x86-base.inc: Don't add live to IMAGE_FSTYPES, default instead

2017-06-28T19:55:08+00:00

Using += makes it difficult to remove. Soft-set with ?= instead. (From OE-Core rev: df850ff9e101afcc9983f907570abaf17421ba0f) Signed-off-by: California Sullivan Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

qemuboot.conf: make cpus match built artifacts

2017-06-23T13:07:52+00:00

Currently, the qemu CPUs for are specified as generic, but the built artifacts are not. For example, we build x86-64 artifacts targeting core2duo but run them in qemu with generic qemu/kvm CPUs. This causes some packages that take advantage of the host architecture to crash because they try to use CPU features not advertised by qemu. As an example, Qt uses ssse3. When artifacts linked against Qt and built targeting core2duo attempt to run on a generic qemu/kvm CPU, we get the following crash: Incompatible processor. This Qt build requires the following features: ssse3 We could fix this by making packages like Qt not take advantage of CPU features. However, we will probably keep facing similar issues over time, so it's better to resolve them in a more enduring way. Fix this by making the qemu -cpu arguments match the built artifacts. (From OE-Core rev: 20b3574749420a1fef2cb2e0579584453dd4c5c5) Signed-off-by: Martin Kelly Signed-off-by: Ross Burton Signed-off-by: Richard Purdie