Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.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:59:47 +0100	[thread overview]
Message-ID: <1345881587.4973.34.camel@x121e.pbcl.net> (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:
> 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.
> 

It doesn't look as though the name "ia32-base" really reflects the
contents of this file very accurately.  Most of the bits in here seem to
have more to do with generic PC architecture and would equally apply to
x86-64 (or indeed any architecture -- e.g. "ext2" which doesn't really
seem to be a machine property in any meaningful sense).  Also, a lot of
the stuff in this file seems rather more like distro policy than
architecture/machine definition.

That's not to say that I think the idea of having an include file to
capture a "PC-type" platform (or, at least, the common use-cases for
one) is a bad idea.  If there are multiple platforms which want to do
that then putting the definitions in a common place does seem sensible,
but I think describing it as "ia32-base" is at the same time too
specific and too generic.

>  Also add several new intel-specific XSERVER variables for building
>  XSERVER variables in BSPs.

If these are really intel-specific (and the i915/i965 bits do look like
they are), shouldn't they stay in meta-intel?  It seems like having
variables defined in oe-core, but not referenced by anything in oe-core,
is possibly a recipe for future confusion.

p.





  parent reply	other threads:[~2012-08-25  8:13 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
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 [this message]
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=1345881587.4973.34.camel@x121e.pbcl.net \
    --to=philb@gnu.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