All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] at91bootstrap.inc: Mark COMPATIBLE_MACHINEs.
Date: Wed, 22 Sep 2010 21:10:19 +0200	[thread overview]
Message-ID: <i7dkar$2hg$1@dough.gmane.org> (raw)
In-Reply-To: <4C9950D0.7000907@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

As a general remark to your current patch series, I think there is some
confusion what COMPATIBLE_MACHINE is for. To me it's signals "this
recipe is specific to a *machine*", not "this recipe is missing files to
make it work without other archs/machines".

The cases:

spidermonkey/firefox/numpy: needs jsautocfg.h for each arch, no need for
COMPATIBLE_MACHINE or COMPATIBLE_ARCH, people need to add support for
their archs

u-boot-env/pivotboot: needs a file for each machine to work properly,
but adding an (empty) fallback file is the way to go since it's only
used in deploy/.

Tacking on COMPATIBLE_{MACHINE,HOST} would just hide the problems and
make fixing it more more tedious than it needs to be. For kernel and
uboot C_M is used to make bitbake do the right thing since they all
share the same PN.

That's my take on the situation, dunno if it's the consensus or not.

regards,

Koen

On 22-09-10 02:41, Graham Gower wrote:
> From b90a9fef712cc934863ee786b2d2dedc37d6902d Mon Sep 17 00:00:00 2001
> From: Graham Gower <graham.gower@gmail.com>
> Date: Wed, 22 Sep 2010 09:39:00 +0930
> Subject: [PATCH 1/5] at91bootstrap.inc: Mark COMPATIBLE_MACHINEs.
> 
> 
> Signed-off-by: Graham Gower <graham.gower@gmail.com>
> ---
>  recipes/at91bootstrap/at91bootstrap.inc |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/recipes/at91bootstrap/at91bootstrap.inc b/recipes/at91bootstrap/at91bootstrap.inc
> index 2160f64..dfe143a 100644
> --- a/recipes/at91bootstrap/at91bootstrap.inc
> +++ b/recipes/at91bootstrap/at91bootstrap.inc
> @@ -1,6 +1,7 @@
>  DESCRIPTION = "at91bootstrap: loaded into internal SRAM by AT91 BootROM"
>  SECTION = "bootloaders"
>  
> +COMPATIBLE_MACHINE = "(afeb9260|at91cap9adk|at91sam9g20ek|at91sam9rlek|at91sam9263ek|at91sam9260ek|at91sam9xeek|at91sam9261ek)"
>  SRC_URI = "ftp://www.at91.com/pub/buildroot/${PN}-${PV}.tar.bz2 \
>  	   file://defconfig \
>             "

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMmlSbMkyGM64RGpERAtR1AKChk2g0bwBLsiyDaAsw94CZsWt9fwCfRw0L
bkqI5S6ortqh1+QHpHVQm1s=
=re7X
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2010-09-22 19:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22  0:41 [PATCH] at91bootstrap.inc: Mark COMPATIBLE_MACHINEs Graham Gower
2010-09-22  7:13 ` Marcin Juszkiewicz
2010-09-22  7:36   ` Graham Gower
2010-09-22  8:01     ` Marco Cavallini
2010-09-22 10:36       ` Graham Gower
2010-09-22 18:26         ` Tom Rini
2010-09-22 18:59           ` Koen Kooi
2010-09-22 19:10 ` Koen Kooi [this message]
2010-09-22 21:47   ` Tom Rini
2010-10-16 13:26 ` Ulf Samuelsson

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='i7dkar$2hg$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.