From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Architecture mismatch QA check not fatal?
Date: Mon, 20 Jun 2011 08:55:39 -0500 [thread overview]
Message-ID: <4DFF515B.1040202@windriver.com> (raw)
In-Reply-To: <90AD0E19-73AB-4443-AAC5-D1069E260D2C@dominion.thruhere.net>
On 6/20/11 8:31 AM, Koen Kooi wrote:
>
> Op 20 jun 2011, om 15:29 heeft Phil Blundell het volgende geschreven:
>
>> On Mon, 2011-06-20 at 08:23 -0500, Mark Hatle wrote:
>>> (The minor cases are primarily firmware loaded into off-board cards in PCI
>>> chasis and such.. occasionally these firmware are ELF and of an architecture not
>>> the same as the host.. it's rare, but I have seen it before.)
>>
>> Shouldn't those firmware images just go in a separate package?
Depends on how the system is configured.. Often I see them packaged with the
firmware loader -- which is the proper arch, etc..
> If we do that we can use INSANE_SKIP_firmwarepackage = True, which seems like a good solution.
Ya, as long as we can skip -- or change it to a warning instead of an error.. I
think we're good. Like I said, this is rare and unlikely to be an issue in
anything in oe-core, meta-oe or even the distributions based on oe-core.. but I
have seen it in customer production environments before.
--Mark
> regards,
>
> Koen
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-06-20 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 7:41 Architecture mismatch QA check not fatal? Koen Kooi
2011-06-20 13:23 ` Mark Hatle
2011-06-20 13:29 ` Phil Blundell
2011-06-20 13:31 ` Koen Kooi
2011-06-20 13:55 ` Mark Hatle [this message]
2011-06-20 14:25 ` Koen Kooi
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=4DFF515B.1040202@windriver.com \
--to=mark.hatle@windriver.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 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.