Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [pull-oe-uboot 1/2] u-boot: remove UBOOT_MACHINE and COMPATIBLE_MACHINES
Date: Fri, 27 May 2011 15:04:57 +0100	[thread overview]
Message-ID: <1306505097.2525.457.camel@phil-desktop> (raw)
In-Reply-To: <4DDE9206.7020007@linux.intel.com>

On Thu, 2011-05-26 at 10:46 -0700, Darren Hart wrote:
> Right, it just starts to look rather ugly in the recipe, especially for
> BSPs supporting more than just a couple of machines. I also think that
> having to use machine overrides is an indicator that the mechanism is
> not working for the purpose it was designed for.

Yes, agreed.  But the point I was making in my first mail is that you
don't actually need to use machine overrides at all; just appending to
COMPATIBLE_MACHINE will work fine.

So, to be clear, in the core u-boot.bb you could have:

# These machines are supported by upstream u-boot
COMPATIBLE_MACHINE = "(beagleboard$|at91sam9260ek$)"

and then, in some putative meta-dec overlay, you could have a
u_boot.bbappend which does:

# This patch adds PDP-11 support to u-boot
SRC_URI += "pdp11.patch"
COMPATIBLE_MACHINE .= "|pdp11$"

and everything ought to work out just fine.  The only bit that is
slightly non-obvious is what to do if you don't want the core version of
u-boot to admit any MACHINEs at all but, as I mentioned to Richard, you
can achieve that by setting

COMPATIBLE_MACHINE = "(?!^)"

or something similar.

p.





  reply	other threads:[~2011-05-27 14:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26  5:01 [PATCH 0/2] u-boot updates to make it more bbappend friendly Darren Hart
2011-05-26  5:02 ` [pull-oe-uboot 1/2] u-boot: remove UBOOT_MACHINE and COMPATIBLE_MACHINES Darren Hart
2011-05-26  7:47   ` Jason Kridner
2011-05-26 13:50     ` Darren Hart
2011-05-26 14:08       ` Chris Larson
2011-05-26 10:50   ` Phil Blundell
2011-05-26 14:37     ` Richard Purdie
2011-05-26 16:18       ` Phil Blundell
2011-05-26 17:46         ` Darren Hart
2011-05-27 14:04           ` Phil Blundell [this message]
2011-05-27 15:06             ` Darren Hart
2011-05-27 15:11               ` Phil Blundell
2011-05-26  5:02 ` [pull-oe-uboot 2/2] u-boot: rename u-boot_git.bb to u-boot_${PV}.bb Darren Hart
2011-05-26  7:58   ` Jason Kridner
2011-05-26 13:52     ` Darren Hart

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=1306505097.2525.457.camel@phil-desktop \
    --to=pb@pbcl.net \
    --cc=dvhart@linux.intel.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