linux/poky.git - Mirror of git.yoctoproject.org/poky

	Commit message (Collapse)	Author	Age	Files	Lines
*	arch-powerpc: set PACKAGE_EXTRA_ARCHS	Ilya Yanok	2011-12-22	1	-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 sync	Kumar Gala	2011-08-05	1	-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 issues	Richard Purdie	2011-08-02	1	-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 ppc64	Kumar Gala	2011-08-01	1	-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 handling	Kumar Gala	2011-08-01	1	-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 config	Richard Purdie	2011-07-27	2	-2/+41
\| \| \| \| \| \|	(From OE-Core rev: 3212029f0967dd353fec8cc147d2b95031d1018a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
*	Move architecture specific TARGET_OS mangling into tune files	Richard Purdie	2011-07-25	1	-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 Purdie	2011-07-25	1	-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>