From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Re: fsl-image-test with sabrelite error
Date: Wed, 19 Mar 2014 09:42:57 -0600 [thread overview]
Message-ID: <5329BB01.60003@mlbassoc.com> (raw)
In-Reply-To: <201403191535.s2JFZJOl023393@vivaldi26.register.it>
On 2014-03-19 09:35, pighi@selea.com wrote:
> now i'm trying to bitbake the image fsl-image-test with the sabrelite.
> so i configured MACHINE=imx6qsabrelite then a bitbake fsl-image-test
>
> selecting the sabrelite means that it uses the nitrogen6x.conf
>
> but i have the following error:
> "Nothing RPROVIDES 'cpuburn-neon' (but /home/yocto/IMX6_yocto/fsl-community-bsp/sources/meta-fsl-demos/recipes-fsl/packagegroups/packagegroup-fsl-tools-benchmark.bb RDEPENDS on or otherwise requires it)
> cpuburn-neon was skipped: incompatible with machine imx6qsabrelite (not in COMPATIBLE_MACHINE)
> "
>
> MACHINE=imx6qsabresd it works, but looking to the conf files i can see that the nitrogen6x.conf and the imx6qsabresd.conf includes the same
>
> include conf/machine/include/imx-base.inc
> include conf/machine/include/tune-cortexa9.inc
>
> so the TUNE_MACHINE should be the same.... so i cannot understand the error.
Have you tried setting MACHINE=nitrogen6x? I've found that works
much better in general and functions perfectly on my SabreLite.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-03-19 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 15:35 fsl-image-test with sabrelite error pighi
2014-03-19 15:42 ` Gary Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-19 15:45 pighi
2014-03-19 16:03 pighi
2014-03-20 22:19 ` Otavio Salvador
2014-03-21 8:49 pighi
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=5329BB01.60003@mlbassoc.com \
--to=gary@mlbassoc.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.