Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] base.bbclass: add support for SOC_FAMILY in	COMPATIBLE_MACHINES
Date: Wed, 04 Aug 2010 12:50:53 -0400	[thread overview]
Message-ID: <20100804165053.GB7189@denix.org> (raw)
In-Reply-To: <131E5DFBE7373E4C8D813795A6AA7F0802E9149F9B@dlee06.ent.ti.com>

On Wed, Aug 04, 2010 at 09:11:19AM -0500, Maupin, Chase wrote:
> 
> > Failing that though, testing COMPATIBLE_MACHINE against MACHINE_CLASS
> > probably is more desirable than adding a completely new variable (i.e.
> > SOC_FAMILY) for that purpose.
> 
> From what I've learned it seems that MACHINE_CLASS and SOC_FAMILY are 
> different in what they are trying to accomplish.
> 
> SOC_FAMILY is defining a family of processors and the features that 
> processor has.  Whereas MACHINE_CLASS is defining a type of device and its 
> features which can use different processors.  So basically SOC_FAMILY 
> defines common processors and MACHINE_CLASS defines common end devices.
> 
> This difference is why SOC_FAMILY exists.  We can have many processors that 
> fit into an SOC_FAMILY that can be used across a variety of end applications 
> from DVR to ip net camera to mobile phone.

I guess this conclusion was direved solely from the names of the respective 
variables. As technically both of them are exactly the same - a variable set 
in machine config or include file and used in OVERRIDES...

-- 
Denys



  reply	other threads:[~2010-08-04 17:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03 21:47 [PATCH] base.bbclass: add support for SOC_FAMILY in COMPATIBLE_MACHINES Chase Maupin
2010-08-04  0:19 ` Denys Dmytriyenko
2010-08-04  5:20   ` Khem Raj
2010-08-04 11:17     ` Michael 'Mickey' Lauer
2010-08-04 11:48       ` Phil Blundell
2010-08-04 14:11         ` Maupin, Chase
2010-08-04 16:50           ` Denys Dmytriyenko [this message]
2010-08-04 21:50           ` Phil Blundell
2010-08-04 16:13         ` Denys Dmytriyenko
2010-08-04 16:59           ` Graeme Gregory
2010-08-04 17:21             ` Denys Dmytriyenko
2010-08-04 19:41               ` Graeme Gregory
2010-08-04  9:13   ` Koen Kooi
2010-08-04  9:44     ` Frans Meulenbroeks
2010-08-04 19:02       ` Tom Rini
2010-08-04  9:54 ` Phil Blundell
2010-08-04 19:49   ` Khem Raj
2010-08-04 20:24     ` Maupin, Chase
2010-08-04 21:37       ` Khem Raj
2010-08-04 23:56         ` Koen Kooi
2010-08-05  4:38           ` Khem Raj

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=20100804165053.GB7189@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@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