From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 5/3] conf/machine/include: Start to fill out architecture specific tune include files and tune features
Date: Mon, 25 Jul 2011 12:34:13 -0700 [thread overview]
Message-ID: <4E2DC535.9030406@mentor.com> (raw)
In-Reply-To: <4E2DBC30.9070808@windriver.com>
On 07/25/2011 11:55 AM, Mark Hatle wrote:
> On 7/22/11 1:14 PM, Tom Rini wrote:
>> On 07/22/2011 11:00 AM, Richard Purdie wrote:
>>> These changes revolve around the idea of tune features. These are represented by
>>> 'flag' strings that are included in the TUNE_FEATURES variable.
>>>
>>> Any string included in TUNE_FEATURES should also add a TUNEVALID[<name>] entry so
>>> we can know which flags are available in TUNE_FEATURES and have documentation about
>>> what the flags do. We will add sanity code to error if flags are listed in
>>> TUNE_FEATURES but are not documented in TUNEVALID.
>>>
>>> A given tune configuration will want to define one or more predetermined sets of
>>> _FEATURE flag lists. These are defined in the form TUNE_FEATURES_tune-<name>.
>>> For defined tune configuation, <name> should be added to the AVAILTUNE list so that
>>> we can determine what tune configurations are available. Flags cannot be used in this
>>> case as with TUNEVALID since its useful to be able to build up tune lists from other
>>> TUNE_FEATURES_tune-yyy options.
>>>
>>> A given tune configuration may also define PACKAGE_EXTRA_ARCHS_tune-<name> and
>>> BASE_LIB_tune-<name> to control the multilib location. All options can be overridden
>>> by the distro or local user configuration.
>>>
>>> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>>
>> As a specific nit, we can't use x86_64 in OVERRIDES (using the normal
>> mechanism need base_contains(...). Can we switch to calling it amd64
>> ala Debian/Ubuntu? Aside from that, as I told Mark the other day, this
>> looks good to me.
>>
>
> I actually prefer "x86-64" I think that is a reasonable compromise between the
> x86_64 naming and the need to not use "_".
That causes other problems, no? Top of my head would be that deb/ipk
doesn't allow a dash in that field. Could be mistaken tho...
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-07-25 19:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 14:49 [PATCH 0/3] First round of tune config file updates Richard Purdie
2011-07-22 14:49 ` [PATCH 1/3] bitbake.conf/cross.bbclass: Add ability to dynamically change library location Richard Purdie
2011-07-22 14:49 ` [PATCH 2/3] conf/machine/tune: Overhaul tune include file variables Richard Purdie
2011-07-22 15:03 ` Kumar Gala
2011-07-22 15:13 ` Richard Purdie
2011-07-22 14:49 ` [PATCH 3/3] conf/machine/include: Set TUNE_CCARGS instead of TARGET_CC_ARCH Richard Purdie
2011-07-22 14:54 ` Koen Kooi
2011-07-22 15:11 ` Richard Purdie
2011-07-22 15:15 ` Koen Kooi
2011-07-22 18:00 ` [PATCH 5/3] conf/machine/include: Start to fill out architecture specific tune include files and tune features Richard Purdie
2011-07-22 18:14 ` Tom Rini
2011-07-25 18:55 ` Mark Hatle
2011-07-25 19:34 ` Tom Rini [this message]
2011-07-25 19:39 ` Mark Hatle
2011-07-25 20:39 ` Phil Blundell
2011-07-25 20:43 ` Tom Rini
2011-07-22 18:00 ` [PATCH 4/3] bitbake.conf/classes: Variable cleanup Richard Purdie
2011-07-22 18:01 ` [PATCH 6/3] Move architecture specific TARGET_OS mangling into tune files Richard Purdie
2011-07-25 13:42 ` Richard Purdie
2011-07-25 16:23 ` Phil Blundell
2011-07-27 16:37 ` Richard Purdie
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=4E2DC535.9030406@mentor.com \
--to=tom_rini@mentor.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