From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] tune/arch-powerpc64: keep insync with arch-powerpc.inc
Date: Tue, 02 Aug 2011 21:39:08 +0100 [thread overview]
Message-ID: <1312317548.2344.612.camel@rex> (raw)
In-Reply-To: <1312312720-20828-1-git-send-email-galak@kernel.crashing.org>
On Tue, 2011-08-02 at 14:18 -0500, Kumar Gala wrote:
> * Add DEFAULTTUNE setting
> * Sync TUNE_PKGARCH with:
> commit 20f285728219c1efcc23d8e861902c212893c68d
> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> Date: Tue Aug 2 12:40:06 2011 +0100
>
> tune/ppc: Fix various TUNE_PKGARCH issues
Quick question, are all ppc64 cores ppc32 capable or not?
Cheers,
Richard
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> ---
> .../machine/include/powerpc/arch-powerpc64.inc | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/meta/conf/machine/include/powerpc/arch-powerpc64.inc b/meta/conf/machine/include/powerpc/arch-powerpc64.inc
> index a965d59..daad355 100644
> --- a/meta/conf/machine/include/powerpc/arch-powerpc64.inc
> +++ b/meta/conf/machine/include/powerpc/arch-powerpc64.inc
> @@ -1,8 +1,13 @@
> +DEFAULTTUNE ?= "powerpc64"
> +
> TUNEVALID[m64] = "Power ELF64 standard ABI"
> TUNE_CONFLICTS[m64] = "m32 nf"
> TUNE_CCARGS += "${@bb.utils.contains("TUNE_FEATURES", "m64", "-m64", "", d)}"
> TUNE_ARCH .= "${@bb.utils.contains("TUNE_FEATURES", [ "m64" ], "powerpc64", "", d)}"
>
> +PPCPKGARCH = "${TUNE_ARCH}"
> +TUNE_PKGARCH ?= "${PPCPKGARCH}"
> +
> AVAILTUNES += "powerpc64"
> TUNE_FEATURES_tune-powerpc64 ?= "m64 fpu-hard"
> BASE_LIB_tune-powerpc64 = "lib64"
next prev parent reply other threads:[~2011-08-02 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 19:18 [PATCH] tune/arch-powerpc64: keep insync with arch-powerpc.inc Kumar Gala
2011-08-02 20:39 ` Richard Purdie [this message]
2011-08-02 21:00 ` Kumar Gala
2011-08-03 16:49 ` Richard Purdie
2011-08-03 16:57 ` Kumar Gala
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=1312317548.2344.612.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox