[PATCH] tune/arch-powerpc64: keep insync with arch-powerpc.inc

Subsystems: the rest

STALE5558d

5 messages, 2 authors, 2011-08-03 · open the first message on its own page

[PATCH] tune/arch-powerpc64: keep insync with arch-powerpc.inc

From: Kumar Gala <hidden>
Date: 2011-08-02 19:23:02

* Add DEFAULTTUNE setting
* Sync TUNE_PKGARCH with:
	commit 20f285728219c1efcc23d8e861902c212893c68d
	Author: Richard Purdie [off-list ref]
	Date:   Tue Aug 2 12:40:06 2011 +0100

	    tune/ppc: Fix various TUNE_PKGARCH issues

Signed-off-by: Kumar Gala <redacted>
---
 .../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"
-- 
1.7.3.4


Re: [PATCH] tune/arch-powerpc64: keep insync with arch-powerpc.inc

From: Richard Purdie <hidden>
Date: 2011-08-02 20:43:58

On Tue, 2011-08-02 at 14:18 -0500, Kumar Gala wrote:
* Add DEFAULTTUNE setting
* Sync TUNE_PKGARCH with:
	commit 20f285728219c1efcc23d8e861902c212893c68d
	Author: Richard Purdie [off-list ref]
	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
quoted hunk
Signed-off-by: Kumar Gala <redacted>
---
 .../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"


Re: [PATCH] tune/arch-powerpc64: keep insync with arch-powerpc.inc

From: Kumar Gala <hidden>
Date: 2011-08-02 21:04:57

On Aug 2, 2011, at 3:39 PM, Richard Purdie wrote:
On Tue, 2011-08-02 at 14:18 -0500, Kumar Gala wrote:
quoted
* Add DEFAULTTUNE setting
* Sync TUNE_PKGARCH with:
	commit 20f285728219c1efcc23d8e861902c212893c68d
	Author: Richard Purdie [off-list ref]
	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
yes

- k
quoted
Signed-off-by: Kumar Gala <redacted>
---
.../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"


_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Re: [PATCH] tune/arch-powerpc64: keep insync with arch-powerpc.inc

From: Richard Purdie <hidden>
Date: 2011-08-03 16:54:44

On Tue, 2011-08-02 at 16:00 -0500, Kumar Gala wrote:
On Aug 2, 2011, at 3:39 PM, Richard Purdie wrote:
quoted
On Tue, 2011-08-02 at 14:18 -0500, Kumar Gala wrote:
quoted
* Add DEFAULTTUNE setting
* Sync TUNE_PKGARCH with:
	commit 20f285728219c1efcc23d8e861902c212893c68d
	Author: Richard Purdie [off-list ref]
	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
yes
Should we make the 64 bit include file automatically include the 32 bit
one then?

That would take care of the
quoted
+PPCPKGARCH = "${TUNE_ARCH}"
+TUNE_PKGARCH ?= "${PPCPKGARCH}"
part but we probably should set the DEFAULTTUNE still...

Cheers,

Richard


Re: [PATCH] tune/arch-powerpc64: keep insync with arch-powerpc.inc

From: Kumar Gala <hidden>
Date: 2011-08-03 17:02:12

On Aug 3, 2011, at 11:49 AM, Richard Purdie wrote:
On Tue, 2011-08-02 at 16:00 -0500, Kumar Gala wrote:
quoted
On Aug 2, 2011, at 3:39 PM, Richard Purdie wrote:
quoted
On Tue, 2011-08-02 at 14:18 -0500, Kumar Gala wrote:
quoted
* Add DEFAULTTUNE setting
* Sync TUNE_PKGARCH with:
	commit 20f285728219c1efcc23d8e861902c212893c68d
	Author: Richard Purdie [off-list ref]
	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
yes
Should we make the 64 bit include file automatically include the 32 bit
one then?

That would take care of the
quoted
quoted
+PPCPKGARCH = "${TUNE_ARCH}"
+TUNE_PKGARCH ?= "${PPCPKGARCH}"
part but we probably should set the DEFAULTTUNE still...
Not a bad idea, I'll look at doing that.

- k

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help