From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: tom.zanussi@intel.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] ia32-base.inc: new include file
Date: Sat, 25 Aug 2012 08:35:09 +0100 [thread overview]
Message-ID: <1345880109.14369.92.camel@ted> (raw)
In-Reply-To: <65d8351bbcb9fb6012c296222795f3c938dc5624.1345867875.git.tom.zanussi@intel.com>
On Fri, 2012-08-24 at 23:34 -0500, tom.zanussi@intel.com wrote:
> From: Tom Zanussi <tom.zanussi@intel.com>
>
> This is the ia32-base.inc moved over from meta-intel. See meta-intel
> for the complete history of contributions to this file.
>
> Here's the initial commit text that explains the purpose of this file:
>
> The meta-intel BSPs currently have a number of machine settings common
> to all - factor these out into a common include file.
>
> Also add several new intel-specific XSERVER variables for building
> XSERVER variables in BSPs.
>
> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
> ---
> meta/conf/machine/include/ia32-base.inc | 58 +++++++++++++++++++++++++++++++++
> 1 file changed, 58 insertions(+)
> create mode 100644 meta/conf/machine/include/ia32-base.inc
I'd add that there are several reasons for this. Things like atom-pc
from meta-yocto could do with accessing this file's content for example
so its useful beyond just meta-intel. In the same way we have various
core "tune" files in OE-Core, this one has become something similar for
IA32. There were recently sstate reuse bugs where the lack of a common
include were causing this to get rebuild depending on which machine was
selected.
It also allows the yocto-bsp tools to work with OE-Core where they'd
currently have failures due to recommending this file.
Cheers,
Richard
next prev parent reply other threads:[~2012-08-25 7:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-25 4:32 [PATCH 0/1] add ia32-base.inc tom.zanussi
2012-08-25 4:34 ` [PATCH 1/1] ia32-base.inc: new include file tom.zanussi
2012-08-25 7:35 ` Richard Purdie [this message]
2012-08-25 7:45 ` Koen Kooi
2012-08-25 8:13 ` Khem Raj
2012-08-25 11:53 ` Richard Purdie
2012-08-25 20:20 ` Khem Raj
2012-08-25 11:56 ` Richard Purdie
2012-08-25 14:17 ` Koen Kooi
2012-08-25 15:51 ` Richard Purdie
2012-08-25 7:59 ` Phil Blundell
2012-08-25 11:50 ` Richard Purdie
2012-08-29 22:21 ` [PATCH 0/1] add ia32-base.inc Saul Wold
-- strict thread matches above, loose matches on Subject: below --
2011-11-18 16:59 tom.zanussi
2011-11-18 16:59 ` [PATCH 1/1] ia32-base.inc: new include file tom.zanussi
2011-11-18 19:17 ` Khem Raj
2011-11-18 20:19 ` Tom Zanussi
2011-11-19 14:52 ` Otavio Salvador
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=1345880109.14369.92.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=tom.zanussi@intel.com \
/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