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: [RFC PATCH 2/3] conf/machine: Overhaul tune include files
Date: Tue, 12 Jul 2011 12:25:10 +0100	[thread overview]
Message-ID: <1310469910.20015.1039.camel@rex> (raw)
In-Reply-To: <E040CBE3-4C88-4768-B056-0588A5566BDA@dominion.thruhere.net>

On Tue, 2011-07-12 at 11:30 +0200, Koen Kooi wrote:
> Op 12 jul 2011, om 10:41 heeft Richard Purdie het volgende geschreven:
> > An updated version of this with a few more pieces filled out is
> > available at:
> > 
> > http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/temp4&id=d2a0bf99fd573221f230bb5253b85166997fac69
> 
> If I understand it correctly
> 
> 	TARGET_FPU_armv7a = "hard"
> 	TARGET_FPU ?= "soft"

These actually become the defaults for armv7 since:

meta/conf/machine/include/tune-armv7.inc:

TUNE_FEATURES_tune-armv7 ??= "fpu-hard"

> becomes
> 
> 	TUNE_FEATURES_append_armv7a = " hard"

but the distro can override TUNE_FEATURES_tune-armv7 as required. The
value in question would be "" or "fpu-hard". You'd actually want:

TUNE_FEATURES_tune-armv7_append = "xxx"

or just set it to what you want:

TUNE_FEATURES_tune-armv7 = "fpu-hard neon"

> And
> 
> 	ARM_FP_ABI = "hardfp"
> 
> becomes
> 
> 	TUNE_FEATURES += "callconvention-hard"

Correct.

> And to maintain the status quo for beagleboard/angstrom:
> 
> 	TUNE_FEATURES_append_omap3 = " neon"

There isn't an omap3 tune in there at present but:

meta/conf/machine/include/tune-cortexa8.inc:

TUNE_FEATURES_tune-cortexa8 ??= "hard-fpu neon"

so neon is the default for that platform. I'm imagining that for omap3
we can do something similar.

> I would also add something like the following:
> 
> --- a/meta/classes/base.bbclass
> +++ b/meta/classes/base.bbclass
> @@ -166,7 +166,7 @@ python base_eventhandler() {
>          if name.startswith("BuildStarted"):
>                 bb.data.setVar( 'BB_VERSION', bb.__version__, e.data )
> -               statusvars = ['BB_VERSION', 'TARGET_ARCH', 'TARGET_OS', 'MACHINE', 'DISTRO', 'DISTRO_VERSION','TARGET_FPU']
> +               statusvars = ['BB_VERSION', 'TARGET_ARCH', 'TARGET_OS', 'MACHINE', 'DISTRO', 'DISTRO_VERSION','TUNE_FEATURES']
>                 statuslines = ["%-17s = \"%s\"" % (i, bb.data.getVar(i, e.data, 1) or '') for i in statusvars]

Agreed, that is a useful touch and makes that line in the status way
more useful for other architectures too.

> Finally a small nitpick: debian uses 'hf' as hardfloat suffix and I prefer that over '-hfp'.

Easy to change, I have no real preference.

>  Meego calls it armv8, but let's not go there.

Agreed ;-).

Cheers,

Richard




      reply	other threads:[~2011-07-12 11:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11 15:57 [RFC PATCH 2/3] conf/machine: Overhaul tune include files Richard Purdie
2011-07-11 16:34 ` Koen Kooi
2011-07-11 16:47   ` Richard Purdie
2011-07-11 16:49     ` Richard Purdie
2011-07-11 17:04     ` Koen Kooi
2011-07-12  8:41       ` Richard Purdie
2011-07-12  9:30         ` Koen Kooi
2011-07-12 11:25           ` Richard Purdie [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=1310469910.20015.1039.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