summaryrefslogtreecommitdiffstats
path: root/meta/conf/machine/include/powerpc
Commit message (Collapse)AuthorAgeFilesLines
* conf/machine: use .= instead of += in TUNE_CCARGSMartin Jansa2013-04-292-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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 (From OE-Core rev: b7430ff83760ac29079d20dc7c62f498a0a9d55d) 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>
* arch-powerpc.inc: add altivec as a valid tune featureMatthew McClintock2012-09-281-0/+2
| | | | | | | (From OE-Core rev: 026f8bc59b6c4cc23cc8a706117bf5b3555f2c7a) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/machine: replace TUNE_CONFLICTS with TUNECONFLICTSMartin Jansa2012-07-171-1/+1
| | | | | | | | | | | | * it wasn't consistent with other machine configs * reported 2 months ago.. http://lists.linuxtogo.org/pipermail/openembedded-core/2012-May/022154.html (From OE-Core rev: 3fec966531059b4b21f40be3b22a60edf88c5190) 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>
* conf/machine/include: Cleanup PowerPC tunings to match READMEMark Hatle2012-04-043-7/+26
| | | | | | | | | | | | | | | Cleanup the PowerPC tunings to match the new tuning README file. Default PowerPC to using TUNE_PKGARCH = ${TUNE_PKGARCH_tune-<tune>} Fix AVAILTUNE settings in ppc603e, and ppce500mc to be addative. Correct potentially overlapping "spe" definitions in ppce500 and ppce500v2. (From OE-Core rev: f81f71bcff4bb1032b034b068efe6065113ca9e7) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* arch-powerpc.inc: use default value of TUNE_PKGARCHMatthew McClintock2012-03-221-4/+2
| | | | | | | | | | We can use the default value for TUNE_PKGARCH, and now we just append "-nf" if TARGET_FPU is fpu-soft (From OE-Core rev: c2d96179c00e6600698d3fbc5cf5c95313ab7535) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* arch-powerpc{, 64}.inc: update/add PACKAGE_EXTRA_ARCHS for powerpc/powerpc64Matthew McClintock2012-02-282-3/+2
| | | | | | | (From OE-Core rev: d19298a4915e00f4a91364d64ddc5fb9689b23c9) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* arch-powerpc: set PACKAGE_EXTRA_ARCHSIlya Yanok2011-12-221-2/+4
| | | | | | | | | | | Set PACKAGE_EXTRA_ARCHS for the generic tunes ("powerpc" and "powerpc-nf") thus allowing to use them instead of tuning to the specific CPU. (From OE-Core rev: 5eafbe2d8684ee1c45477bfd69b579af47adccd9) Signed-off-by: Ilya Yanok <yanok@emcraft.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune/arch-powerpc64: include arch-powerpc.inc to keep things in syncKumar Gala2011-08-051-0/+4
| | | | | | | | | | | Added a DEFAULTTUNE setting and included arch-powerpc.inc. This way we pick up the changes to TUNE_PKGARCH and things should be kept more in sync going forward. (From OE-Core rev: 2c9bd779b008be266072f3c6d79430f63ec02241) Signed-off-by: Kumar Gala <galak@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune/ppc: Fix various TUNE_PKGARCH issuesRichard Purdie2011-08-021-1/+2
| | | | | | | | | | We need to ensure only one value ends up in TUNE_PKGARCH rather than several. This change ensures consistency accross all the PPC tune files and that they correctly inherit the core value but also allow it to be overwritten. (From OE-Core rev: f9a8b719dd3fc7593a509c8f288caf1486add2f8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune/arch-powerpc64: Remove support for soft-float from ppc64Kumar Gala2011-08-011-4/+2
| | | | | | | | | | All 64-bit PPC processors support hard-float so no need to support soft-float. (From OE-Core rev: 54c7d1faf5376c8fb9b19f4e192ce959c8442782) Signed-off-by: Kumar Gala <galak@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune/arch-powerpc64: Fix typo with 64-bit TUNE_CCARGS handlingKumar Gala2011-08-011-1/+1
| | | | | | | | | | When figuring out how to set TUNE_CCARGS we should look for 'm64' not 'n64' in TUNE_FEATURES. (From OE-Core rev: 7a9ea28e69e8121a559f610dd2330edd33f0a907) Signed-off-by: Kumar Gala <galak@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add basic PowerPC core tune configRichard Purdie2011-07-272-2/+41
| | | | | | (From OE-Core rev: 3212029f0967dd353fec8cc147d2b95031d1018a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Move architecture specific TARGET_OS mangling into tune filesRichard Purdie2011-07-251-0/+2
| | | | | | (From OE-Core rev: f10a3457cdfbb4a94978da998d178d4254632fa7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/machine/include: Start to fill out architecture specific tune include ↵Richard Purdie2011-07-251-0/+1
files and tune features These changes revolve around the idea of tune features. These are represented by 'flag' strings that are included in the TUNE_FEATURES variable. Any string included in TUNE_FEATURES should also add a TUNEVALID[<name>] entry so we can know which flags are available in TUNE_FEATURES and have documentation about what the flags do. We will add sanity code to error if flags are listed in TUNE_FEATURES but are not documented in TUNEVALID. A given tune configuration will want to define one or more predetermined sets of _FEATURE flag lists. These are defined in the form TUNE_FEATURES_tune-<name>. For defined tune configuation, <name> should be added to the AVAILTUNE list so that we can determine what tune configurations are available. Flags cannot be used in this case as with TUNEVALID since its useful to be able to build up tune lists from other TUNE_FEATURES_tune-yyy options. A given tune configuration may also define PACKAGE_EXTRA_ARCHS_tune-<name> and BASE_LIB_tune-<name> to control the multilib location. All options can be overridden by the distro or local user configuration. (From OE-Core rev: 5f9d56bd64997b93ed7e46c117851002a0556654) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-14 01:31:16 +0000