[meta-freescale] [meta-fsl-arm-extra][PATCH] broadcom-nvram-config: Add compatible machine setting
John Weber
rjohnweber at gmail.com
Mon Mar 25 08:34:12 PDT 2013
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 at 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)"
>
More information about the meta-freescale
mailing list