summaryrefslogtreecommitdiff
path: root/meta/conf/machine/include
AgeCommit message (Collapse)AuthorFiles
2017-04-05x86-base.inc, qemuarm.conf: prefer 4.10 version of linux-yoctoMartin Jansa1
* 4.8 version was removed in: commit 466e6e45ca04a07ebe1b1f52de747f077b362d54 Author: Bruce Ashfield <bruce.ashfield@windriver.com> Date: Tue Mar 28 08:58:07 2017 -0400 linux-yocto: drop 4.8 recipes We have 4.1 (LTSI), 4.4 (LTS), 4.9 (LTS/LTSI) and 4.10 available in master. 4.8 is no longer required, so we drop the recipe to keep the version selection under control. * causing each build to start with 188 lines of this stuff: NOTE: preferred version 4.8% of linux-yocto not available (for item virtual/kernel) NOTE: versions of linux-yocto available: 4.1.38+gitAUTOINC+7140ddb86e_4d2c95e78c 4.10.5+gitAUTOINC+01f18cba44_b97dcd4f06 4.4.56+gitAUTOINC+271b0c8d51_01aaede0a2 4.9.17+gitAUTOINC+8b97a445fa_3ff3760c2a NOTE: preferred version 4.8% of linux-yocto not available (for item kernel-module-raid456) NOTE: versions of linux-yocto available: 4.1.38+gitAUTOINC+7140ddb86e_4d2c95e78c 4.10.5+gitAUTOINC+01f18cba44_b97dcd4f06 4.4.56+gitAUTOINC+271b0c8d51_01aaede0a2 4.9.17+gitAUTOINC+8b97a445fa_3ff3760c2a Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-03-21feature-arm-thumb.inc: fix ARM_THUMB_SUFFIX for armv8Andre McCurdy1
The current definition for ARM_THUMB_SUFFIX doesn't consider armv8 and will therefore cause TUNE_PKGARCH to be set incorrectly for machines which inherit arch-armv8 and don't include aarch64 in TUNE_FEATURES (ie when building for 32bit ARMv8). Also fix typo in comments and improve TUNEVALID[thumb] wording. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-03-10conf/machine/include: enable hardfloat by default for ARMv6 and aboveAndre McCurdy10
Defaulting to softfp probably isn't the best choice anymore, especially as there are now ARM BSP layers which leave DEFAULTTUNE entirely up to the distro: https://lists.yoctoproject.org/pipermail/yocto/2017-February/034637.html Also add 't' to the ARMv7 default DEFAULTTUNEs, since there's no clear reason to default to ignoring ARM_INSTRUCTION_SET for ARMv7. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-03-04arch-mips: Fix tune configuration for mipsisa64r6el-n32-nfZubair Lutfullah Kakakhel1
Big endian flag marked in a little endian configuration by mistake. Remove it. Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-03-01recipes: Make use of the new bb.utils.filter() functionPeter Kjellerstedt3
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-02-23arch-arm*.inc: squash whitespace within TUNE_FEATURES stringsAndre McCurdy5
TUNE_FEATURES is include in BUILDCFG_VARS, so any whitespace is visible to the user during the build process. Remove the extra whitespace added during the 2.1 development cycle: http://git.openembedded.org/openembedded-core/commit/?id=f774b44fa007a2a756ada892ede832b1251d940c For consistency, squash whitespace within PACKAGE_EXTRA_ARCHS strings too. Whitespace within TUNE_FEATURES strings in the tune-cortexa*.inc files has been fixed in a separate commit: http://git.openembedded.org/openembedded-core/commit/?id=5610c6397ee098dd998b7417b343494de77179f9 (From OE-Core rev: 3cd0c5ef748ad072f1bd9a8d42157e9643bf97eb) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-01-23runqemu: fixes for slirp, network device and hostfwdRobert Yang1
Fixed: - Add QB_NETWORK_DEVICE to set network device, it will be used by both slirp and tap. - Set QB_NETWORK_DEVICE to "-device virtio-net-pci" in qemuboot.bbclass but runqemu will default to "-device e1000" when QB_NETWORK_DEVICE is not set, this is because oe-core's qemu targets support virtio-net-pci, but the one outside of oe-core may not, "-device e1000" is more common. - Set hostfwd by default: 2222 -> 22, 2323 -> 23, and it will choose a usable port when the one like 222 is being used. This can avoid conflicts when multilib slirp qemus are running. We can forward more ports by default if needed, and bsp.conf can custom it. - Use different mac sections for slirp and tap to fix conflicts when running both of them on the same host. [YOCTO #7887] CC: Nathan Rossi <nathan@nathanrossi.com> CC: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
2016-12-22arch-mips: Add MIPS 64r6 N32 tuneZubair Lutfullah Kakakhel1
Add MIPS64R6-n32 tuning options. Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-16meta: remove True option to getVar callsJoshua Lock5
getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?\(( ?[^,()]*), True\) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-07arch-mips: sort new MACHINEOVERRIDES by priorityAndré Draszik1
While I couldn't find explicit documentation, it appears that the list of MACHINEOVERRIDES should be sorted from less specific to more specific left to right, so that more specific overrides take precedence. Signed-off-by: André Draszik <adraszik@tycoint.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-12-07tune-cortexa*.inc: squash whitespace within TUNE_FEATURES stringsAndre McCurdy6
TUNE_FEATURES is include in BUILDCFG_VARS, so any whitespace is visible to the user during the build process. Remove the extra whitespace added during the 2.1 development cycle: http://git.openembedded.org/openembedded-core/commit/?id=f774b44fa007a2a756ada892ede832b1251d940c For consistency, squash whitespace within PACKAGE_EXTRA_ARCHS strings too. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-11-30arch-arm64.inc: Include arch-armv7ve.incKhem Raj1
All armv8 implementations from a53 - a73 supports virtual extentions Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-11-15arch-mips: Add MACHINEOVERRIDES variables to reduce duplicationZubair Lutfullah Kakakhel2
In some cases, each MIPS variant in a recipe requires a duplicate line. Even if the passed flag is the same. Add global MACHINEOVERRIDES variables for the following * mipsarch : All MIPS * mipsarch{eb,el} : All MIPS Big/Little Endian * mipsarchr6 : All MIPS R6 * mipsarcho32 : All MIPS o32 Endian Independent * mipsarchn32 : All MIPS n32 Endian Independent * mipsarchn64 : All MIPS n64 Endian Independent * mipsarcho32{eb,el} : All MIPS o32 Big/Little Endian * mipsarchn32{eb,el} : All MIPS n32 Big/Little Endian * mipsarchn64{eb,el} : All MIPS n64 Big/Little Endian This is intended to reduce duplications in recipes [YOCTO #10404] Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-11-15arch-mips: Add o32 in TUNE_FEATURES for MIPS32R6Zubair Lutfullah Kakakhel1
mips32r6 tunings should have o32 ABI flag in TUNE_FEATURES Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-11-06runqemu: add user mode (SLIRP) support to x86 QEMU targetsTodor Minchev1
Using 'slirp' as a command line option to runqemu will start QEMU with user mode networking instead of creating tun/tap devices. SLIRP does not require root access. By default port 2222 on the host will be mapped to port 22 in the guest. The default port mapping can be overwritten with the QB_SLIRP_OPT variable e.g. QB_SLIRP_OPT = "-net nic,model=e1000 -net user,hostfwd=tcp::2222-:22" Signed-off-by: Todor Minchev <todor.minchev@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-10-31conf: Use xf86-input-libinput by defaultJussi Kukkonen2
Don't install legacy X input drivers for any machines by default, RRECOMMEND xf86-input-libinput instead. This is the setup suggested by upstream: install only libinput by default, but let niche legacy drivers sort higher in configuration so they get chosen if installed. So the order is: evdev < libinput < (synaptics|vmmouse|...) This also removes vmmouse X driver from the qemu config. If a VMware virtual mouse device really needs to be supported, we should enable CONFIG_MOUSE_PS2_VMMOUSE in kernel instead: that is directly supported by the libinput X driver. Fixes [YOCTO #10195]. Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-10-15arch-mips.inc: remove duplicates from PACKAGE_ARCHSRobert Yang1
Fixed: MACHINE = "qemumips64" DEFAULTTUNE = "mips64-o32" $ bitbake linux-yocto ERROR: OE-core's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: Error, the PACKAGE_ARCHS variable contains duplicates. The following archs are listed more than once: mips64-o32 Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-10-15x86-base: Update version to 4.8Saul Wold1
This update will avoid confusion with other parts of OE-Core that set the kernel version to 4.8 for qemux86* and genericx86*. Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-10-07arch-mips: Add mipsisa{32, 64}r6{el, } tunesZubair Lutfullah Kakakhel4
Add support for MIPS Release 6 ISA and the various tune configurations. This patch adds the tunes for 32r6 and 64r6 n64 and not the n32 variants at the moment. Release 6 onwards, the tuples are now - mipsisa32r6-linux-gnu - mipsisa32r6el-linux-gnu - mipsisa64r6-linux-gnuabi64 - mipsisa64r6el-linux-gnuabi64 - mipsisa64r6-linux-gnuabin32 - mipsisa64r6el-linux-gnuabin32 For more details, check https://wiki.debian.org/Multiarch/Tuples Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-27machine/qemu*: Add comment regarding the reason for virtio-rng-pciNathan Rossi2
Bring across the comment that was in runqemu regarding why the virtio-rng-pci device was needed. This comment is added to each location where the virtio-rng-pci device is added. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-23arch-mips: Add mips64-o32 tunesZubair Lutfullah Kakakhel1
Add mips64 + o32 rootfs abi tune configurations Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-23tune-ppc[65]00.inc: Disable QEMU usermode usageOtavio Salvador2
The QEMU usermode fails with invalid instruction error when used with those tunes. The issue is being tracked in [YOCTO: #10304]. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-23arch-mips: Add mips64r2 tunesZubair Lutfullah Kakakhel1
Add MIPS64r2 optimizations Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-23runqemu: Move virtio RNG to machine configurationNathan Rossi2
Not all QEMU machines (outside of those available in OE-Core) are capable of using the virtio-rng-pci device due to various machine models not having a pci/virtio bus. This makes it such that the use of the '-device virtio-rng-pci' flag to QEMU is machine specific. This patch removes the general addition of the flag to all runqemu targets and adds the flag into the QB_OPT_APPEND for all the qemu* machines in OE-Core that support its use (which is all of them). Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-09-16qemuboot-x86: Add task_timeout = -1 to uvesafbSaul Wold1
This causes the default timeout to be set to infinity, it will still report out every 5000 milliseconds Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09qemu.inc: inherit qemuboot.bbclassRobert Yang1
All qemu boards should be able to boot by runqemu. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09qemumips/qemumips64.conf: set vars for runqemuRobert Yang1
Add qemuboot-mips.inc to reduce duplicated code, the various mips bsps which can be boot by runqemu can require qemuboot-mips.inc Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-09qemux86.conf/qemux86-64.conf: set vars for runqemuRobert Yang1
Add qemuboot-x86.inc to reduce duplicated code, the x86/x86_64 bsps which can be boot by runqemu can require qemuboot-x86.inc. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-03arch-mips.inc: Disable QEMU usermode usage when building with n32 ABIAlexander Kanavin1
QEMU usermode doesn't support n32 binaries, erroring with "Invalid ELF image for this architecture". Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-08-01tune-mips-24k: add QEMU_EXTRAOPTIONS for DSP and MIPS16e coresAndré Draszik1
The core emulated by default by qemu-mips(el) just crashes with illegal instruction when encountering DSP and/or MIPS16e instructions - we have to specify a CPU that supports the extra instructions. This is an issue when generating a rootfs and e.g. running some of the package postinstall scriptlets. The patch to qemu to add 24KEc as a CPU has been accepted upstream, so let's use that CPU here as well as needed. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-07-10tune-ppce500mc.inc: pass -mcpu=e500mc for ppce500mc kernel compileZhenhua Luo1
Currently the -mcpu parameter is not passed to cross gcc when assembling kernel .S file, the implicit -mcpu option that defaults to the latest server cpu might casuse incorrect assembling. A existent case is that wait instruction of ppce500mc is incorrectly assembled to power9 version with default -mcpu setting, accordingly kernel boot calltrace happend when wait instruction is executed on ppce500mc targets. Signed-off-by: Zhenhua Luo <zhenhua.luo@nxp.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-06-12mips: add tunes for (some) 24K coresAndré Draszik1
- add 24kc big and little endian, which is based on mips32r2 w/o FPU - add 24kec which is 24kc + DSP - both can have the MIPS16e ASE enabled in their tunes Signed-off-by: André Draszik <adraszik@tycoint.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-06-12mips: add a tune for using MIPS16e ASE instructionsAndré Draszik1
The MIPS16e instruction set still has to be enabled by setting MIPS_INSTRUCTION_SET = 'mips16e' in e.g. distro.conf and can be disabled on a per-recipe basis as needed. This is a similar approach as is available on ARM for Thumb support. Note that contrary to the ARM Thumb support in OE, we do add a new OVERRIDE (mips16e), as there are some recipes in OE that need to be compiled slightly differently if mips16e mode is requested. Signed-off-by: André Draszik <adraszik@tycoint.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-05-14feature-arm-vfp.inc: fix overzealous ARMPKGSFX_FPU modificationAndré Draszik1
Since commit 972b4fc (feature-arm-neon.inc: restore vfpv3-d16 support) we're replacing _all_ dashes (-) in ARMPKGSFX_FPU, which is causing problems for all legitimate uses of the dash as TUNE_PKGARCH doesn't have the right value anymore: E.g. on raspberrypi2: ERROR: OE-core's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: Error, the PACKAGE_ARCHS variable (all any noarch armv5hf-vfp armv5thf-vfp armv5ehf-vfp armv5tehf-vfp armv6hf-vfp armv6thf-vfp armv7ahf-vfp armv7at2hf-vfp armv7vehf-vfp armv7vet2hf-vfp armv7vehf-neon armv7vet2hf-neon armv7vehf-neon-vfpv4 armv7vet2hf-neon-vfpv4 cortexa7hf-vfp cortexa7hf-neon cortexa7hf-neon-vfpv4 cortexa7t2hf-vfp cortexa7t2hf-neon cortexa7t2hf-neon-vfpv4 raspberrypi3) for DEFAULTTUNE (cortexa7thf-neon-vfpv4) does not contain TUNE_PKGARCH (cortexa7hf-neonvfpv4). Fix this by being more explicit about what we're modifying. Reported-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-05-11feature-arm-neon.inc: restore vfpv3-d16 supportAndré Draszik2
Commit 6661718 (feature-arm-{neon,vfp}.inc: refactor and fix issues) effectively changed the gcc -mfpu= option from -mfpu=vfpv3-d16 to -mfpu=vfpv3d16, which gcc doesn't understand. Restore the original value. After doing that, we also need to adjust ARMPKGSFX_FPU which should contain the same value without dash '-' as it is used that way throughout. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-05-06tune-mips32r2.inc: add soft-float variantsAndré Draszik1
Signed-off-by: André Draszik <adraszik@tycoint.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-05-06arch-powerpc64.inc: disable the use of qemu usermode on ppc64Alexander Kanavin1
It simply does not work at all: https://lists.yoctoproject.org/pipermail/yocto/2016-April/029698.html Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-05-06arch-armv7ve: inherit armv7a tunes fileDenys Dmytriyenko1
armv7a is a subset of armv7ve: https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html -march=armv7ve is the armv7-a architecture with virtualization extensions. By inheriting armv7a from armv7ve it's possible for e.g. Cortex-A15 machines to include tune-cortexa15.inc and have a full range of optimizations, but set DEFAULTTUNE as "armv7a" to produce binaries compatible with Cortex-A8 machines, etc. Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-28bitbake.conf: rename 'gobject-introspection-data' machine feature to ↵Alexander Kanavin1
'qemu-usermode' The new value is more general and better reflects what having the feature really means. Introspection data, then, is built only if 'gobject-introspection-data' is in DISTRO_FEATURES and 'qemu-usermode' is in MACHINE_FEATURES. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-24x86-base.inc: suggest the latest kernelMaxin B. John1
Use latest 4.x kernel instead of 3.x version Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-03-23tune-arm926ejs: Handle missing thumb suffixJens Rehsack1
When enabling tune for arm926ejs, poky optionally appends suffixes for thumb and dsp support. Since sometimes arm926ejse (ARM code) and sometime arm926ejste (thumb code) is used in PACKAGE_ARCH, allow both. Signed-off-by: Jens Rehsack <sno@netbsd.org> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-03-12machine/include/arch-x86: Make x32 ABI not supporting gobject-introspection-dataRichard Purdie1
x32 isn't supported by user mode qemu so we can't build gobject-introspection-data, so disable it in this case. (From OE-Core rev: 4ee1eb8ddd3fbe144fbaeb32e07b66e191aa7548) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-09tune-corei7.inc: Fix PACKAGE_EXTRA_ARCHS for corei7-32Chang Rebecca Swee Fun1
Change the name to core2-32 from core2. There's no AVAILTUNES with the name core2. Make sure that we specify the correct TUNE name so PACKAGE_EXTRA_ARCHS is expanded correctly. [ YOCTO #9197 ] Signed-off-by: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com> Signed-off-by: Anuj Mittal <anujx.mittal@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-07tune-cortexa17.inc: apply changes similar to a15Trevor Woerner1
Apply the same sort of changes to the Cortex-A17 tune as were done in commit 35392025f3236f5e5393f9cf0857732da9a2e503. Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-06feature-arm-thumb.inc: Fix thumb tune override warningNathan Rossi1
Fix the quotes in the bb.utils.contains feature check so that the call results in a boolean value instead of a string, which allows the warning check to occur. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-28tune-cortexa9.inc: add vfpv3 tunesRichard Tollerton1
Define tunnings to enable 32 register VFPv3 for cortexa9 processor cores More details: http://www.arm.com/products/processors/technologies/vector-floating-point.php Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-15qemu.inc: Add rng-tools to qemu imagesSaul Wold1
This patch adds rng-tools to MACHINE_EXTRA_RRECOMMENDS so that can be used to provide the additional entropy to prevent hangs in getrandom() for qemu images [YOCTO #8681] [YOCTO #8816] Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-11tune-corei7.inc: tell qemu to emulate a matching processorRoss Burton1
If tune-corei7 is in use then the target binaries may contain instructions that qemu-x86-64 can't execute by default, resulting in errors on rootfs construction: NOTE: Running intercept scripts: NOTE: > Executing update_font_cache intercept ... qemu: uncaught target signal 4 (Illegal instruction) - core dumped In this case the instruction is popcnt, part of SSE4.2, so tell Qemu to emulate the CPU that the tune targets (in this case, Nehalem). Also pass check=false as the Nehalem machine supports VME but user-space qemu doesn't, which produces a warning unless CPUID checking is disabled. [ YOCTO #8888 ] Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-02-02machine/include: drop tune-cortexm*.inc and tune-cortexr4.incAndre McCurdy3
The Cortex M1, M3 and R4 CPU tuning files are poorly tested (if at all). They have no obvious users either inside or outside oe-core. Until OE officially gains support for CPUs without an MMU, these tuning files are probably better maintained outside of oe-core (e.g. in a separate meta-nommu layer). Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-30gcc, qemuppc: Explicitly disable forcing SPE flagsKhem Raj1
G4 does not have SPE, so we make that explicit in the tune files and since we emulate G4 when building Qemu, we ensure it for qemuppc as well. GCC config for powerpc-linux is made to include SPE by default which is equivalent if the tripet was powerpc-linux*spe, this forces gcc to configure assembler to enable -mspe by default, when we do that then the kernel fails to compile with binutils 2.26, since newer assembler is smart to detect the tlbia instructions are not compatible with SPE and hence the kernel build breaks rightly. We configure the kernel for G4 as well where it enables tlbia instrucitons rightly so because it thinks its being configured for power4. So we keep the options but do not force -mspe down to assembler as default. Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-12 16:30:18 +0000