From: Gary Thomas <samoht.yrag@gmail.com>
To: meta-freescale@yoctoproject.org
Subject: Re: i.MX6Q VPU firmware missing for core-image-basic
Date: Wed, 04 Dec 2013 06:17:32 -0700 [thread overview]
Message-ID: <529F2B6C.6020402@gmail.com> (raw)
In-Reply-To: <529F1EFE.9080600@mlbassoc.com>
On 2013-12-04 05:24, Gary Thomas wrote:
> On 2013-12-04 05:13, Otavio Salvador wrote:
>> On Wed, Dec 4, 2013 at 10:00 AM, Tarek El-Sherbiny
>> <tarek.elsherbiny@gmail.com> wrote:
>>> I mad some progress now.
>>>
>>> core-imgae-base ---> VPU FW is included.
>>> core-imgae-basic ---> VPU FW is not included. !!!!?
>>>
>>> Does anyone understand why?
>>>
>>> I know that the firmware is picked up in MACHINE_EXTRA_RRECOMMENDS variable
>>> but I don't know why it affects only core-imgae-base and not
>>> core-imgae-basic !
>>>
>>> Hope someone could shed some light here.
>>
>> core-image-base: A console-only image that fully supports the target
>> device hardware.
>> ...
>> core-image-basic: A console-only image with more full-featured Linux
>> system functionality installed.
>>
>> The image names are misleading, I agree. Please bring this to OE-Core
>> for discussion.
>>
>
> I sent a patch for this to OE-core in October which seems to have
> been ignored :-(
> http://lists.openembedded.org/pipermail/openembedded-core/2013-October/085750.html
>
BTW, the patch has been applied to OE-core master, but not the dora branch.
prev parent reply other threads:[~2013-12-04 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 15:32 i.MX6Q VPU firmware missing for core-image-basic Tarek El-Sherbiny
2013-12-04 12:00 ` Tarek El-Sherbiny
2013-12-04 12:13 ` Otavio Salvador
2013-12-04 12:24 ` Gary Thomas
2013-12-04 13:17 ` Gary Thomas [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=529F2B6C.6020402@gmail.com \
--to=samoht.yrag@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.