From: Elvis Dowson <elvis.dowson@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Elvis Dowson <elvis.dowson@gmail.com>
Subject: [meta-xilinx] tune-ppc440.inc: Update support for the PowerPC 440 processor in the Xilinx Virtex-5 FXT FPGA.
Date: Thu, 31 May 2012 08:23:11 +0200 [thread overview]
Message-ID: <1338445392-39723-1-git-send-email-elvis.dowson@gmail.com> (raw)
This commit updates support for the PowerPC 440 processor in the Xilinx
Virtex-5 FXT FPGA.
Signed-off-by: Elvis Dowson <elvis.dowson@gmail.com>
---
conf/machine/include/tune-ppc440.inc | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/conf/machine/include/tune-ppc440.inc b/conf/machine/include/tune-ppc440.inc
index f77f628..394364d 100644
--- a/conf/machine/include/tune-ppc440.inc
+++ b/conf/machine/include/tune-ppc440.inc
@@ -4,11 +4,11 @@ require conf/machine/include/powerpc/arch-powerpc.inc
TUNEVALID[ppc440] = "Enable ppc440 specific processor optimizations"
TUNE_CCARGS += "${@bb.utils.contains("TUNE_FEATURES", "ppc440", "-mcpu=440", "", d)}"
-TUNE_PKGARCH = "${@bb.utils.contains("TUNE_FEATURES", "ppc440", "ppc440", "${PPCPKGARCH}", d)}"
-TARGET_FPU = "soft"
AVAILTUNES += "ppc440"
-TUNE_FEATURES_tune-ppc440 = "m32 ppc440"
-PACKAGE_EXTRA_ARCHS_tune-ppc440 = "ppc440"
+TUNE_FEATURES_tune-ppc440 = "m32 fpu-soft ppc440"
+TUNE_PKGARCH_tune-ppc440 = "ppc440"
+PACKAGE_EXTRA_ARCHS_tune-ppc440 = "${PACKAGE_EXTRA_ARCHS_tune-powerpc-nf} ppc440"
-#MACHINEOVERRIDES .= "ppc440"
+# glibc configure options to get 440 specific library (for sqrt)
+GLIBC_EXTRA_OECONF += "${@bb.utils.contains("TUNE_FEATURES", "ppc440", "-with-cpu=440", "", d)}"
--
1.7.9.5
next reply other threads:[~2012-05-31 6:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 6:23 Elvis Dowson [this message]
2012-05-31 15:15 ` [meta-xilinx] tune-ppc440.inc: Update support for the PowerPC 440 processor in the Xilinx Virtex-5 FXT FPGA Adrian Alonso
2012-05-31 16:53 ` Elvis Dowson
2012-06-01 4:18 ` Adrian Alonso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1338445392-39723-1-git-send-email-elvis.dowson@gmail.com \
--to=elvis.dowson@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.