[PATCH 0/1] tune-ppc476.inc: support ppc476

[PATCH 0/1] tune-ppc476.inc: support ppc476

[Peter Seebach]

One of the BSPs we support uses a 476-family chip, so we have a
tuning for it in our custom toolchain layer. Sending a tuning upstream
too because someone else might want it. Has been lightly tested with
the oe-core toolchain; it at least allows compiles.

The following changes since commit 20405bdab18b7a2b101f818e72863d289d5945e4:
  Bruce Ashfield (1):
        linux-yocto/3.0: perf scripting support

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib seebs/ppc476
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/ppc476

Peter Seebach (1):
  tune-ppc476.inc: Support ppc476

 meta/conf/machine/include/tune-ppc476.inc |   14 ++++++++++++++
 1 files changed, 14 insertions(+), 0 deletions(-)
 create mode 100644 meta/conf/machine/include/tune-ppc476.inc

[PATCH 1/1] tune-ppc476.inc: Support ppc476

[Peter Seebach]

A couple of boards use chips which perform noticably better
when optimized for the 476. Add a trivial tune file to let
them run better.

Signed-off-by: Peter Seebach <peter.seebach@windriver.com>
---
 meta/conf/machine/include/tune-ppc476.inc |   14 ++++++++++++++
 1 files changed, 14 insertions(+), 0 deletions(-)
 create mode 100644 meta/conf/machine/include/tune-ppc476.inc

diff --git a/meta/conf/machine/include/tune-ppc476.inc b/meta/conf/machine/include/tune-ppc476.inc
new file mode 100644
index 0000000..5d10261
--- /dev/null
+++ b/meta/conf/machine/include/tune-ppc476.inc
@@ -0,0 +1,14 @@
+DEFAULTTUNE ?= "ppc476"
+
+require conf/machine/include/powerpc/arch-powerpc.inc
+
+TUNEVALID[ppc476] = "Enable ppc476 specific processor optimizations"
+TUNE_CCARGS += "${@bb.utils.contains("TUNE_FEATURES", "ppc476", "-mcpu=476", "", d)}"
+
+AVAILTUNES += "ppc476"
+TUNE_FEATURES_tune-ppc476 = "m32 fpu-hard ppc476"
+TUNE_PKGARCH_tune-ppc476 = "ppc476"
+PACKAGE_EXTRA_ARCHS_tune-ppc476 = "${PACKAGE_EXTRA_ARCHS_tune-powerpc} ppc476"
+
+# glibc configure options to get 476 specific library (for sqrt)
+GLIBC_EXTRA_OECONF += "${@bb.utils.contains("TUNE_FEATURES", "ppc476", "-with-cpu=476", "", d)}"
-- 
1.7.0.4

Re: [PATCH 1/1] tune-ppc476.inc: Support ppc476

[Khem Raj]

On Mon, Jul 16, 2012 at 10:58 AM, Peter Seebach
<peter.seebach@windriver.com> wrote:
> +GLIBC_EXTRA_OECONF += "${@bb.utils.contains("TUNE_FEATURES", "ppc476", "-with-cpu=476", "", d)}"

have you built an OE internal toolchain with this successfully.?

Re: [PATCH 0/1] tune-ppc476.inc: support ppc476

[Saul Wold]

On 07/16/2012 10:58 AM, Peter Seebach wrote:
> One of the BSPs we support uses a 476-family chip, so we have a
> tuning for it in our custom toolchain layer. Sending a tuning upstream
> too because someone else might want it. Has been lightly tested with
> the oe-core toolchain; it at least allows compiles.
>
> The following changes since commit 20405bdab18b7a2b101f818e72863d289d5945e4:
>    Bruce Ashfield (1):
>          linux-yocto/3.0: perf scripting support
>
> are available in the git repository at:
>
>    git://git.yoctoproject.org/poky-contrib seebs/ppc476
>    http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/ppc476
>
> Peter Seebach (1):
>    tune-ppc476.inc: Support ppc476
>
>   meta/conf/machine/include/tune-ppc476.inc |   14 ++++++++++++++
>   1 files changed, 14 insertions(+), 0 deletions(-)
>   create mode 100644 meta/conf/machine/include/tune-ppc476.inc
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
Merged into OE-Core

Thanks
	Sau!