Openembedded Core Discussions
 help / color / mirror / Atom feed
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: Wed, 03 Aug 2011 17:49:57 +0100	[thread overview]
Message-ID: <1312390197.2344.702.camel@rex> (raw)
In-Reply-To: <992464A7-1010-4A47-BFAA-A7F93C683C99@kernel.crashing.org>

On Tue, 2011-08-02 at 16:00 -0500, Kumar Gala wrote:
> On Aug 2, 2011, at 3:39 PM, Richard Purdie wrote:
> 
> > 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
> 
> yes

Should we make the 64 bit include file automatically include the 32 bit
one then?

That would take care of the

>> +PPCPKGARCH = "${TUNE_ARCH}"
>> +TUNE_PKGARCH ?= "${PPCPKGARCH}"

part but we probably should set the DEFAULTTUNE still...

Cheers,

Richard




  reply	other threads:[~2011-08-03 16:54 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
2011-08-02 21:00   ` Kumar Gala
2011-08-03 16:49     ` Richard Purdie [this message]
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=1312390197.2344.702.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