summaryrefslogtreecommitdiff
path: root/meta/conf/machine
AgeCommit message (Collapse)AuthorFiles
2014-01-28tune: README: Whitespace cleanupDarren Hart1
Before making content changes, cleanup the various whitespace errors in this file. Mostly end-of-line whitepsace. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-28tune: Remove tune-x86_64.incDarren Hart1
The tune-x86_64.inc file is conceptually flawed. x86_64 is more akin to the x86 and x86-32 ABIs defined in arch-x86.inc than it is a concrete tune file, such as i586 or core2 - to the extent that everything but the default tune is defined in the arch-x86.inc file. This becomes very apparant when attempting to include tune-x86_64.inc in the x86 tune hierarchy. Remove the tune-x86_64.inc tune file in favor of it being an ABI definition in arch-x86.inc and relying on the linear hierarchy of concrete cpu-types in tune-i586, tune-core2, and tune-corei7. core2_64 should suffice in lieu of x86_64 for all but a couple esoteric corner cases involving older pre-core2 CPUs. In these cases, if they exist at all, the BSP can replace the include tune-x86_64.inc with arch-x86.inc and set the default tune to x86_64. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-28tune-corei7: Add support for cpu-type corei7Darren Hart1
corei7 offers a significant advancement since the previous core2 cpu-type described in the tune-core2 file. From the GCC(1): Intel Core i7 CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1 and SSE4.2 instruction set support. This offers optimizations for Nehalem and Silvermont (e.g. Bay Trail) CPUs (and beyond). Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-28tune: Make 32b or 64b explicit in tune name for core2Darren Hart1
Core2 has both a 32b and a 64b variant. Currently, core2 implies 32b, while core2_64 is the 64b version. This implicit 32b mode will become confusing in later architectures, such as corei7, where it would be natural for people to assume "corei7" meant 64 bit. Rather than carrying forward an implicit 32b mode and rather than changing the naming scheme part way through the architecture hiearchy, make the 32b and 64b variant explicit in the tune name by changing core2 to core2-32. This patch also standardises on using '-' in the names. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-28tune-core2: Only add the current ARCH to PACKAGE_EXTRA_ARCHSDarren Hart1
Inherit the PACKAGE_EXTRA_ARCHS from i586 and only explicitly add core2 here. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-28tune-core2: Replace -mtune=generic with -mtune=core2Darren Hart1
-march specifies which ISA to use. -mtune specifies which cpu-type to optimize instruction ordering for, but not which ISA to use. There are times when it may make sense to specify mtune=generic and use a more specific march, such as core2, but the opposite makes little sense at all: use cpu-type specific ISA, but order the instructions generically. While the -mtune is implied by -march, gcc does not verify it is using -mtune=core2 with: gcc -Q -march=core2 --help=target Explicitly specify -mtune=core2 to be sure. Add a comment header describing the CPUs targeted by this tune file. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-28i586: Only add the current tune to PACKAGE_EXTRA_ARCHSDarren Hart1
The generic x86 build supports i586 by default, so this specific tune file technically doesn't add any specific ARCHes to PACKAGE_EXTRA_ARCHS. For consistency, append the current tune to PACKAGE_EXTRA_ARCHS. Since we do not have specific tune files for i386 and i486, just drop them. These could be added to tune-x86 version if there is a need to maintain them, but they really do not belong here. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-28x86: Replace ia32 with x86 when referring to the generic architectureDarren Hart6
ia32 implies 32bit, while these files provide descriptions for IA32, X86_64, and X32 architectures. The term "x86" fits this used better without resorting to using the term "Intel" which isn't quite right as it excludes things like the tune-c3 file describing a Via CPU. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Paul Eggleton <paul.eggleton@intel.com> Cc: Tom Zanussi <tom.zanussi@intel.com> Cc: Nitin Kamble <nitin.a.kamble@intel.com> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-11-21ia32-base: Remove cpio and ext3 defaultsRichard Purdie1
On real IA hardware, neither the ext3 or cpio images are particularly useful or used. cpio is legacy from initramfs and that specific image now overrides FSTYPES accordingly. The size difference in filesystems makes ext3 as a file format less useful, mainly being useful in the qemu case. When needed users can still override the default FSTYPES so having saner defaults makes sense. This improves build times and uses less network bandwidth for builds and releases. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-11-20ia32-base.inc: remove eee-acpi-scripts from MACHINE_EXTRA_RRECOMMENDSPaul Eggleton1
We shouldn't bring this in unconditionally for all ia32 machines. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-09-24qemu: don't claim support for IrDA and PCMCIARoss Burton1
QEMU machines don't have virtual IrDA or PCMCIA hardware, so don't claim to support them. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-11ia32-base: only depend on GL if opengl DISTRO_FEATURE enabledRoss Burton1
As Mesa refuses to compile if the "opengl" DISTRO_FEATURE isn't enabled, mesa-driver-i9xx and the GLX X module have to be conditional in the ia32 machine defintion too. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-11qemu: only depend on mesa-driver-swrast if opengl is enabledRoss Burton3
As Mesa refuses to compile if the "opengl" DISTRO_FEATURE isn't enabled, mesa-driver-swrast has to be conditional in the QEMU machine defintions too. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-09qemu.inc: remove apm as a MACHINE_FEATURESaul Wold1
APM is not only obsolete, but requires a kernel config enabled and is meaningless for QEMU VM [YOCTO #5121] Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-20qemuppc: Change default tune to 74xxKhem Raj1
We use mac99 as platform for qemuppc lets choose a tuning thats appropriate for it Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-08-20tune-ppc7400.inc: Add tune fileKhem Raj1
This is appropriate tune for mac99/g4 platform that we use for emulating qemuppc Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-08-16qemu, default-providers: Add mesa as default virtual/eglMartin Jansa1
* it's safer to select it consistently with virtual/libgl* providers Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-12tune-cortexa*.inc: fix tunings for cortex a5, a7, a8, a9, a15 machines.Andy Voltz7
Using CORTEX_ID variable reference in the tuning overrides did not work. This reverts those changes, and adds a tuning file for the cortex-a5. Revert "tune-cortexa5.inc: Add tune file for cortex-a5" Revert "tune-cortexa.inc: create a common include for cortex-a armv7a tuning" Signed-off-by: Andy Voltz <andy.voltz@timesys.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-07tune-cortexa5.inc: Add tune file for cortex-a5Andy Voltz1
Signed-off-by: Andy Voltz <andy.voltz@timesys.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-07tune-cortexa.inc: create a common include for cortex-a armv7a tuningAndy Voltz6
The tuning files for the cortex-a* processors are mostly identical for the A7,A8,A9,A15 processors. Rework these files to use a CORTEX_ID variable to setup the tuning for each specific processor. Signed-off-by: Andy Voltz <andy.voltz@timesys.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-05-31qemu*: restrict NFSD to linux-yocto onlyBruce Ashfield1
In the current releases, not all linux-yocto derived kernels have NFS support, or NFS support fragments availble. To ensure that derived kernels like linux-yocto-cutom continue to work against poky-lsb, we can make the KERNEL_FEATURE append more specific to the linux-yocto recipe. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-16machine/qemumips64: Add machine definitionKhem Raj1
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-05-08qemu: Ensure kernel nfsd module is enabledSaul Wold1
This will ensure that qemu images that include the nfs-server package have the kernel feature correctly enabled Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-05-03ia32-base.inc: remove inapropriate grub dependencyTomas Frydrych1
There is no good reason for ia32 machines to have hard dependency on grub, as there are other bootloaders available for ia32 platforms. Signed-off-by: Tomas Frydrych <tomas@sleepfive.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-01tune-thumb.inc: Remove, replaced by arm/feature-arm-thumb.incMartin Jansa1
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-04-29conf/machine: use .= instead of += in TUNE_CCARGSMartin Jansa42
* number of TUNE_CCARGS conditionals is important if we add extra space with each one in "else" branch I'm building for 2 MACHINEs one is cortexa9, second is cortexa8 few months ago we added TUNE_CCARGS[vardepvalue] in bitbake.conf http://git.openembedded.org/openembedded-core/commit/?id=03f1e34ea3ce80931e9c3cd2ab22824f28a7233b which fixed some cases (like mentioned tune-xscale and tune-arm926ejs) where both had unused TUNE_CCARGS when common DEFAULTTUNE was used. with cortexa[89] it's different, because cortexa9 has one extra TUNE_CCARGS TUNE_CCARGS += "${@bb.utils.contains("TUNE_FEATURES", "cortexa9", "-mtune=cortex-a9", "", d)}" which adds extra *space* even when not used because of '+=' and as result: $ bitbake-diffsigs tmp-eglibc/sstate-diff/1366797730/*/armv7*/adapterbase/*do_configure* basehash changed from f986789fb8fb3579ed6a3492cc8a8d10 to c851b5f838d945ee13072e9ad6725dca Variable TUNE_CCARGS value changed from ' -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon ' to ' -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon ' Hash for dependent task gcc-runtime_4.7.bb.do_populate_sysroot changed from bdeabf7a86958b9110b566344b7916de to 2be5618e6bc8c57ec9db5659bf217915 Hash for dependent task eglibc_2.17.bb.do_populate_sysroot changed from b4f40fc62dde684acd0a574532a55360 to 97fcb426603d4a1c1099c0504d2ebf7d Hash for dependent task glib-2.0_2.34.3.bb.do_populate_sysroot changed from fd2f90b83098c34e88d649d70f6ea4f5 to ebd740bb94ea3eb0a914efda6fc82c4a Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-03-27qemux86*.conf: replace XSERVER weak assignment with a hard oneLaurentiu Palcu2
Because the qemu.inc is now included before the XSERVER assignment, the xf86-video-vmware and xf86-video-vmmouse are not built and the X for qemux86 and qemux86-64 does not start. [YOCTO #4124] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-25conf/machine: Clean up MACHINEOVERRIDES handlingRichard Purdie8
OVERRIDES reads from left to right, least to most specific. We were appending to MACHINEOVERRIDES when we should have been prepending so the ordering of qemuall verses qemuxxx was incorrect, as was the x86 override and several of the arm overrides. This patch is a batch cleanup of the various issues to correct the order from least to most specific. The include order does matter and we needed to tweak some of that in this patch too. [YOCTO #4090] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-22mesa: rename mesa-dri recipe to just mesaLaurentiu Palcu4
Rename mesa-dri recipes to just mesa. Also, replace all references to mesa-dri in all recipes/configs. The reason for this renaming (quote from bugzilla): "mesa-dri is a artefact of mesa-xlib existing, which doesn't anymore. mesa-dri should be renamed to mesa." [YOCTO #3385] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-18tune-xscale: Drop unneeded optimisation overridesRichard Purdie1
These hacks have been around for years and deal with old gcc issues. They've been removed from the other use sites, we should clean up the core tune file too. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-09tune-cortexa*: Fix TUNE_FEATURES and PACKAGE_EXTRA_ARCHS for thf-neonMartin Jansa4
* all cortexa*thf-neon except cortexa8 were missing thumb feature from TUNE_FEATURES_tune-armv7athf-neon * all cortexa*thf-neon except cortexa8 included cortexa9t2-vfp instead of cortexa9t2hf-vfp * PACKAGE_EXTRA_ARCHS_tune-cortexa8thf-neon was including from armv7a -PACKAGE_EXTRA_ARCHS_tune-armv7ahf-neon +PACKAGE_EXTRA_ARCHS_tune-armv7athf-neon * please do more testing for this, I'm sending this commit mostly because I've noticed that new a7 and a15 differ from a8 more then I've expected and I don't have any a7/a15 MACHINEs, feel free to extend http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/tune2-test to add and test fake a7/a15 configs Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-09soc-family: fix SOC_FAMILY override orderChase Maupin1
* the current order has SOC_FAMILY settings, which are generic settings for a group of devices, overriding the machine specific settings. For example: KERNEL_DEVICETREE_ti33x = "xxxx" KERNEL_DEVICETREE_beaglebone = "yyyy" Should yield "yyyy" when building for the beaglebone because that is a more specific device than ti33x. However, without this change the result is that the value is set to "xxxx" meaning the more generic setting overrides the more specific setting. Signed-off-by: Chase Maupin <Chase.Maupin@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-07tune-cortexa7: add tunes for ARM Cortex-A7Denys Dmytriyenko1
http://www.arm.com/products/processors/cortex-a/cortex-a7.php Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-03-07tune-cortexa15: add tunes for ARM Cortex-A15Denys Dmytriyenko1
http://www.arm.com/products/processors/cortex-a/cortex-a15.php Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-02-17conf: Remove unused ROOT_FLASH_SIZE variable from the configHolger Hans Peter Freyther1
This variable is set but never used in OE-core and meta-oe. It was historically used for the Opie collection but seems to be unused now. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-25meta: remove all mention of PCMCIA_MANAGERRoss Burton1
Nothing appears to use this anymore, and it's been a very long time since there was anyone expressing an interest in the alternatives. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-22qemu.inc: Define preferred providers for libgl, libgles1 and libgles2Khem Raj1
This is needed to to boot efl images on qemuarm,qemumips and qemuppc these options were already defined for qemux86 and qemux86-64 and therefore the images were booting fine for these two machines Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-16qemu: machine override ability addedCristian Iorga1
Add override ability to qemu to allow qemu specific configurations for any qemu machine. Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-16ia32-base.inc: Add more macros for xf86 driversNitin A Kamble1
This commit adds macros for fbdev & modesetting X driver packages. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-12-03tune-cortexa*: add another TUNE which allows to enable cortexa* together ↵Martin Jansa2
with thumb and neon * like we have with tune-armv7at-neon Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-12-03arch-armv6: add tunes without vfp enabledVíctor Enríquez1
This work was made by Victor Enriquez and then modified by Denis Carikli who was helped by Mark Hatle comments. And in the end modified by Martin Jansa to support different ARMPKGARCH and removed explicit -novfp suffix. The changes are for adding support to armv6-novfp, for building binaries for armv6 machines without vfp, for example the htc dream. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org> Signed-off-by: Víctor Enríquez <victor.quicksilver@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-12-03arch-armv4.inc: add --fix-v4bx to TARGET_LD_KERNEL_ARCH only for armv4 and ↵Martin Jansa1
strongarm1100 * without this patch it does apply --fix-v4bx not only to armv4, but also all higher (because they also have armv4 in TUNE_FEATURES) * it causes SIGILL on armv4t http://lists.linuxtogo.org/pipermail/openembedded-devel/2012-November/042298.html * someone please test on armv4 device (I tested only bitbake -e output that it's correctly applied with DEFAULTTUNE == armv4 * maybe we can should fix this in binutils instead (both 2.22 and 2.23 are affected) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-12-03arch-arm*: unify appending to TUNE_FEATURESMartin Jansa5
* that we always use TUNE_FEATURES_tune-arm* variable and add only one TUNE_FEATURE to it * for bigendian always use littleendian counterpart and append bigendian TUNE_FEATURE Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-12-03arch-armv[457]*: fix PACKAGE_EXTRA_ARCHS for bigendian TUNEsMartin Jansa3
* bigendian should not include little endian PACKAGE_ARCHS Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-12-03arch-armv5: fix missing thumb TUNE_FEATURE in armv5t-vfp and following tunesMartin Jansa1
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-12-03tune-*: add PACKAGE_EXTRA_ARCHS entries starting with specific ARMPKGARCHMartin Jansa12
* e.g. arm926ejs DEFAULT tune is compatible with all PACKAGE_EXTRA_ARCHS_tune-armv5te, but needs to list arm926ejs with all possible suffixes too Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-12-03tune-cortexa*, tune-xscale: fix ARMPKGARCHMartin Jansa3
* hf/t/neon/b suffix is added by other ARMPKGSFX* variables, should not be part of ARMPKGARCH, otherwise resulting TUNE_PKGARCH have that suffix twice, e.g. cortexa8hf-neonhf-neon Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-26tune-*: define more generic DEFAULTTUNE to share feed between machinesMartin Jansa9
* this is mostly for backwards compatibility and to share binary feed like it was before, but now without missing different -mtune in it * if you want to build some package with -mtune add something like this to your distro config DEFAULTTUNE_qemuarm_pn-openssl = "arm926ejs" DEFAULTTUNE_qemuarmx_pn-openssl = "xscale" be aware that if you do this you should do it also for all packages which depends on openssl because if you dont and you build e.g. dhcp, then dhcp build for arm926ejs (even with DEFAULTTUNE armv5te) will depend on openssl with arm926ejs, so dhcp in armv5te feed will be rebuild after each MACHINE switch. * cortexm3, cortexr4, iwmmx and ep9312 are using own DEFAULTTUNE because they define also different -march * shared feeds are armv4t: arm920t, arm9tdmi armv5te: arm926ejs, xscale armv7a-neon: cortexa8, cortexa9 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-26arch-arm: define different ARMPKGARCH when different CCARGS are usedMartin Jansa13
* without this tune-xscale and tune-arm926ejs were both creating packages in armv5te feed, but each with different -mtune, with OEBasicHash enabled it was causing each package to rebuild with new -mtune after MACHINE switch, but that doesn't make sense with output stored in the same armv5te feed * this makes different feed for each -mtune, but more generic one to be selected with DEFAULTTUNE * tune-iwmmxt and tune-ep9312 were already using this, just move it bellow AVAILTUNES and use ARMPKGARCH_tune-foo syntax * tune-cortexr4 and tune-cortexm3 are using armv7r/armv7m as ARMPKGARCH because there isn't another tune to use the same -march Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-26arm/arch-arm*: define ARMPKGARCH_tune-* for default tunesMartin Jansa6
* tune-foo is not valid override, for it to work I had to add ARMPKGARCH = "${ARMPKGARCH_tune-${DEFAULTTUNE}}" but that doesn't work without value defined for every supported DEFAULTTUNE value, otherwise it's expanded like this TUNE_PKGARCH (${ARMPKGARCH_tune-armv5te}te). Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-13 15:46:52 +0000