All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Weber <rjohnweber@gmail.com>
To: meta-freescale@yoctoproject.org
Subject: Re: [meta-fsl-arm-extra][PATCH] broadcom-nvram-config: Add compatible machine setting
Date: Mon, 25 Mar 2013 10:34:12 -0500	[thread overview]
Message-ID: <51506E74.4070805@gmail.com> (raw)
In-Reply-To: <1364215919-13865-1-git-send-email-otavio@ossystems.com.br>

Otavio -

I thought the point of setting:

BROADCOM_FIRMWARE = "INVALID"

was to throw an error on purpose in case someone added the package to their 
machine and did not modify the recipe to provide a corresponding nvram file for 
their machine?

Doesn't adding COMPATIBLE_MACHINE remove that error?

John

On 3/25/13 7:51 AM, Otavio Salvador wrote:
> This avoid a warning, during recipe parsing of bitbake, due an
> incompatible machine as the nvram.txt is not available as no know
> default one is suitable for every board so a specific one is need.
>
> Change-Id: I409a1310c6f37975a46d79cdbd84665daa381e0d
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
>   recipes-bsp/broadcom-nvram-config/broadcom-nvram-config.bb | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config.bb b/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config.bb
> index 0afd374..85f56d2 100644
> --- a/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config.bb
> +++ b/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config.bb
> @@ -26,3 +26,4 @@ BROADCOM_FIRMWARE_wandboard-dual = "bcm4329"
>
>   RDEPENDS_${PN} = "linux-firmware-${BROADCOM_FIRMWARE}"
>
> +COMPATIBLE_MACHINE = "(wandboard-dual)"
>


  reply	other threads:[~2013-03-25 15:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 12:51 [meta-fsl-arm-extra][PATCH] broadcom-nvram-config: Add compatible machine setting Otavio Salvador
2013-03-25 15:34 ` John Weber [this message]
2013-03-25 17:31   ` Otavio Salvador
2013-03-25 18:27     ` John Weber

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=51506E74.4070805@gmail.com \
    --to=rjohnweber@gmail.com \
    --cc=meta-freescale@yoctoproject.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.