sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity
generic-poky/meta/conf/machine/include/tune-ppce500mc.inc

15 lines
633 B
PHP
Raw Normal View History

Add basic PowerPC core tune config (From OE-Core rev: 3212029f0967dd353fec8cc147d2b95031d1018a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-07-26 11:36:53 +00:00
DEFAULTTUNE ?= "ppce500mc"
conf/machine/include: Start to fill out architecture specific tune include 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>
2011-07-22 16:32:21 +00:00
require conf/machine/include/powerpc/arch-powerpc.inc
conf/machine/tune: Overhaul tune include file variables There is currently consideradble confusion over how the tune files operate and how these interact with the rest of the build system. This update/overhaul changes things so the tune files are primarily resonsible for setting: TUNE_ARCH - What was formerly set as TARGET_ARCH and is the value that represents the architecture we're targetting. TUNE_PKGARCH - The value that represents the tune confuration that this set of tune parameters results in. This allows the significant improvement that the core can now always determine the target architecture value, even when TARGET_ARCH needs to be reset to something different and likewise, there is one package architecture variable the core can reference allowing simplification of the BASE_PACKAGE_ARCH, PACKAGE_ARCH and FEED_ARCH variables. (From OE-Core rev: a10de4cf8b424ee95c8e283e75d486be5b3b8eac) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-07-22 13:15:20 +00:00
Add basic PowerPC core tune config (From OE-Core rev: 3212029f0967dd353fec8cc147d2b95031d1018a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-07-26 11:36:53 +00:00
TUNEVALID[ppce500mc] = "Enable ppce500mc specific processor optimizations"
conf/machine: use .= instead of += in TUNE_CCARGS * 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>
2013-04-24 13:42:12 +00:00
TUNE_CCARGS .= "${@bb.utils.contains("TUNE_FEATURES", "ppce500mc", " -mcpu=e500mc", "", d)}"
Add basic PowerPC core tune config (From OE-Core rev: 3212029f0967dd353fec8cc147d2b95031d1018a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-07-26 11:36:53 +00:00
conf/machine/include: Cleanup PowerPC tunings to match README 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>
2012-03-30 19:31:20 +00:00
AVAILTUNES += "ppce500mc"
tune-ppce500mc: Adjust PowerPC e500mc tune file to correctly set hard fpu. (From OE-Core rev: 1456cdef9e1a28f7abe1385b10caa5069ba7afac) Signed-off-by: Malcolm Crossley <malcolm.crossley@ge.com> Signed-off-by: Kumar Gala <galak@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-07-28 21:47:07 +00:00
TUNE_FEATURES_tune-ppce500mc = "m32 fpu-hard ppce500mc"
conf/machine/include: Cleanup PowerPC tunings to match README 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>
2012-03-30 19:31:20 +00:00
TUNE_PKGARCH_tune-ppce500mc = "ppce500mc"
arch-powerpc: set PACKAGE_EXTRA_ARCHS 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>
2011-09-07 15:38:36 +00:00
PACKAGE_EXTRA_ARCHS_tune-ppce500mc = "${PACKAGE_EXTRA_ARCHS_tune-powerpc} ppce500mc"
tune-ppc: Update to pass glibc configure option to get cpu specific support We need --with-cpu based to glibc to get proper support on 603e & e500mc to pickup proper math libs to deal with sqrt. These core do not implement the fsqrt[s] instructions that the normal PPC math libs utilize. This causes use to not set AVAILTUNES specifically to the sub-arch only as we arent generically compatiable. (From OE-Core rev: 078699cb8c707830c86b55787fd535d87171388e) Signed-off-by: Kumar Gala <galak@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-08-12 04:53:50 +00:00
# glibc configure options to get e500mc specific library (for sqrt)
GLIBC_EXTRA_OECONF += "${@bb.utils.contains("TUNE_FEATURES", "ppce500mc", "-with-cpu=e500mc", "", d)}"