From: Phil Blundell <philb@gnu.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: qemuarm: should it really have TUNE_ARCH armv5te?
Date: Tue, 11 Sep 2012 18:37:23 +0100 [thread overview]
Message-ID: <1347385043.29443.28.camel@x121e.pbcl.net> (raw)
In-Reply-To: <20120911173529.GL14077@jama.jama.net>
On Tue, 2012-09-11 at 19:35 +0200, Martin Jansa wrote:
> If this works then DISTRO would have finer control of which DEFAULTTUNE
> to use
>
> 1) default: don't use mtune, optimize only for march (don't mix mtune in
> the same feed).
>
> 2) include optimized-tune.inc in distro.conf: use mtune only for some packages, but
> with separate package feed for them
>
> 3) DEFAULTTUNE = ${OPTDEFAULTTUNE} in distro.conf: always use best mtune
> available for MACHINE, but unlike current default, don't mix them in
> same package feed
>
> DEFAULTTUNE = ${OPTDEFAULTTUNE} should also be used for PACKAGE_ARCH ==
> MACHINE_ARCH
Yeah, that all sounds fairly reasonable to me. I'm not sure that
optimized-tune.inc belongs in oe-core, since its contents is inherently
distro-specific, but the general plan seems pretty good.
p.
next prev parent reply other threads:[~2012-09-11 17:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 13:01 qemuarm: should it really have TUNE_ARCH armv5te? Martin Jansa
2012-09-11 13:48 ` Martin Jansa
2012-09-11 15:51 ` ARM-tuning -- was " Mark Hatle
2012-09-11 15:59 ` Martin Jansa
2012-09-11 16:09 ` Mark Hatle
2012-09-11 16:22 ` Martin Jansa
2012-09-11 16:13 ` Koen Kooi
2012-09-11 18:40 ` Khem Raj
2012-09-11 18:53 ` Phil Blundell
2012-09-11 19:58 ` Khem Raj
2012-09-11 16:46 ` Phil Blundell
2012-09-11 16:53 ` Martin Jansa
2012-09-11 17:14 ` Phil Blundell
2012-09-11 17:21 ` Martin Jansa
2012-09-11 17:35 ` Martin Jansa
2012-09-11 17:37 ` Phil Blundell [this message]
2012-09-11 17:43 ` Martin Jansa
2012-09-11 18:00 ` Mark Hatle
2012-09-12 14:33 ` Richard Purdie
2012-09-13 6:20 ` Martin Jansa
2012-09-13 10:42 ` Richard Purdie
2012-09-13 12:14 ` Martin Jansa
2012-09-13 12:58 ` Richard Purdie
2012-09-15 7:01 ` Martin Jansa
2012-09-21 15:52 ` Martin Jansa
2012-09-22 11:48 ` Richard Purdie
2012-09-13 16:47 ` Mark Hatle
2012-09-13 17:02 ` Phil Blundell
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=1347385043.29443.28.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=martin.jansa@gmail.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