From: Nikolay Dimitrov <picmaster@mail.bg>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm-extra][PATCH v2] riotboard: Fix broken image builds against linux-fslc
Date: Thu, 30 Apr 2015 01:46:24 +0300 [thread overview]
Message-ID: <55415F40.30700@mail.bg> (raw)
In-Reply-To: <CAP9ODKpZPK44f7e61fUh2cQWAmkMe8kktc3XFuNSBKwuGJSHHQ@mail.gmail.com>
Hi Otavio,
On 04/30/2015 12:41 AM, Otavio Salvador wrote:
> On Wed, Apr 29, 2015 at 6:38 PM, Nikolay Dimitrov <picmaster@mail.bg>
> wrote:
>> Several Yocto images fail to build because they're using packages
>> that require imx6-specific hardware support (ASRC, VPU, GPU3D),
>> which is not available in the mainline kernel. This patch fixes the
>> following image builds: - core-image-minimal - core-image-base -
>> fsl-image-multimedia
>>
>> Signed-off-by: Nikolay Dimitrov <picmaster@mail.bg>
>
> Without the image provided by Fabio, fsl-image-machine-test will fail
> ;)
Right now fsl-image-machine-test fails on riotboard even with the added:
PREFERRED_VERSION_imx-test = "00.00.00"
I'm not saying this config is not needed. What I'm saying is that I
have a build failure that probably masks the need for this config.
Regards,
Nikolay
next prev parent reply other threads:[~2015-04-29 22:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 21:38 [meta-fsl-arm-extra][PATCH v2] riotboard: Fix broken image builds against linux-fslc Nikolay Dimitrov
2015-04-29 21:41 ` Otavio Salvador
2015-04-29 22:46 ` Nikolay Dimitrov [this message]
2015-04-29 22:59 ` Fabio Estevam
2015-04-30 2:50 ` Nikolay Dimitrov
2015-04-30 3:22 ` Nikolay Dimitrov
2015-04-30 10:52 ` Otavio Salvador
2015-04-30 14:34 ` Nikolay Dimitrov
2015-04-30 15:13 ` Fabio Estevam
2015-04-30 15:18 ` Nikolay Dimitrov
2015-04-29 21:42 ` Gary Thomas
2015-04-29 21:48 ` Otavio Salvador
2015-04-29 21:55 ` Nikolay Dimitrov
2015-04-29 21:51 ` Nikolay Dimitrov
2015-04-29 21:56 ` Gary Thomas
2015-04-29 22:12 ` Nikolay Dimitrov
2015-04-29 22:36 ` Gary Thomas
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=55415F40.30700@mail.bg \
--to=picmaster@mail.bg \
--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.