All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Weber <rjohnweber@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm-extra][PATCH] broadcom-nvram-config: Add compatible machine setting
Date: Mon, 25 Mar 2013 13:27:12 -0500	[thread overview]
Message-ID: <51509700.2060300@gmail.com> (raw)
In-Reply-To: <CAP9ODKrnzfyXy8BPA0ce_cApLxLZRTUZxTDU0mm10Qqph9tm5w@mail.gmail.com>

OK.  I understand now.  Sounds good.

On 3/25/13 12:31 PM, Otavio Salvador wrote:
> On Mon, Mar 25, 2013 at 12:34 PM, John Weber <rjohnweber@gmail.com> wrote:
>> 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?
>
> It will do in rootfs generation as linux-firmware-INVALID won't be instalable.
>
>> Doesn't adding COMPATIBLE_MACHINE remove that error?
>
> Yes but the reason I added it is because bitbake try to checksum a
> nvram.txt file which does not exist to other machines and then do a
> warning during recipe parsing.
>
> --
> Otavio Salvador                             O.S. Systems
> E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
> Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br
>


      reply	other threads:[~2013-03-25 18:27 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
2013-03-25 17:31   ` Otavio Salvador
2013-03-25 18:27     ` John Weber [this message]

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=51509700.2060300@gmail.com \
    --to=rjohnweber@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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.