Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] tune-mips32.inc: Add mips32-nf and mips32el-nf
Date: Tue, 07 Feb 2012 20:00:34 -0800	[thread overview]
Message-ID: <4F31F362.7040201@linux.intel.com> (raw)
In-Reply-To: <4F2A88F2.60906@opendreambox.org>

On 02/02/2012 05:00 AM, Andreas Oberritter wrote:
> tune-mips32.inc only lists mips32 CPUs with hardware FPU.
> Extend it to list CPUs without hardware FPU, too.
>
> Signed-off-by: Andreas Oberritter<obi@opendreambox.org>
> ---
>   meta/conf/machine/include/tune-mips32.inc |    6 +++++-
>   1 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/meta/conf/machine/include/tune-mips32.inc b/meta/conf/machine/include/tune-mips32.inc
> index 4a5f0fa..45d865e 100644
> --- a/meta/conf/machine/include/tune-mips32.inc
> +++ b/meta/conf/machine/include/tune-mips32.inc
> @@ -6,9 +6,13 @@ TUNEVALID[mips32] = "Enable mips32 specific processor optimizations"
>   TUNE_CONFLICTS[mips32] = "n64 n32"
>   TUNE_CCARGS += "${@bb.utils.contains("TUNE_FEATURES", "mips32", "-march=mips32", "", d)}"
>
> -AVAILTUNES += "mips32 mips32el"
> +AVAILTUNES += "mips32 mips32el mips32-nf mips32el-nf"
>   TUNE_FEATURES_tune-mips32 = "${TUNE_FEATURES_tune-mips} mips32"
>   PACKAGE_EXTRA_ARCHS_tune-mips32 = "mips"
>   TUNE_FEATURES_tune-mips32el = "${TUNE_FEATURES_tune-mipsel} mips32"
>   PACKAGE_EXTRA_ARCHS_tune-mips32el = "mipsel"
> +TUNE_FEATURES_tune-mips32-nf = "${TUNE_FEATURES_tune-mips-nf} mips32"
> +PACKAGE_EXTRA_ARCHS_tune-mips32-nf = "mips-nf"
> +TUNE_FEATURES_tune-mips32el-nf = "${TUNE_FEATURES_tune-mipsel-nf} mips32"
> +PACKAGE_EXTRA_ARCHS_tune-mips32el-nf = "mipsel-nf"
>

Merged into OE-core

Thanks
	Sau!



      reply	other threads:[~2012-02-08  4:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02 13:00 [PATCH] tune-mips32.inc: Add mips32-nf and mips32el-nf Andreas Oberritter
2012-02-08  4:00 ` Saul Wold [this message]

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=4F31F362.7040201@linux.intel.com \
    --to=sgw@linux.intel.com \
    --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