From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Re: yocto SDK for imx6 sabrelite board. (armel vs armhf)
Date: Wed, 13 Aug 2014 08:22:24 -0600 [thread overview]
Message-ID: <53EB74A0.3050804@mlbassoc.com> (raw)
In-Reply-To: <CAHUo2cxM+FpD-kw5wUV1B=vt8ujY2ZBLsQpOkkNxEsdL2Ln8qA@mail.gmail.com>
On 2014-08-13 08:15, ss infod wrote:
> Does anyone have any input on this ?
>
> Thanks
> ssinfod
>
>
> On Tue, Aug 12, 2014 at 8:02 AM, ssinfod ssinfod <ssinfod@gmail.com <mailto:ssinfod@gmail.com>> wrote:
>
> Hello,
>
> I just built an image with SDK for the imx6 sabrelite. (ie: MACHINE ??= 'imx6qsabrelite')
> Command: bitbake core-image-full-cmdline -c populate_sdk
>
> I noticed that the SDK toolchain is based on "gnueabi" instead of "gnueabihf".
>
> Here is the list from the opt directory:
> dev@dev-i3:/opt/poky/1.6+snapshot$ ls
> environment-setup-cortexa9hf-vfp-neon-poky-linux-gnueabi
> site-config-cortexa9hf-vfp-neon-poky-linux-gnueabi
> sysroots
> version-cortexa9hf-vfp-neon-poky-linux-gnueabi
> dev@dev-i3:/opt/poky/1.6+snapshot$ version-cortexa9hf-vfp-neon-poky-linux-gnueabi
>
> I thought that the imx6 was a armhf device.
> Why is the default toolchain using "gnueabi" and not "gnueabihf" for the sabrelite target ?
>
> Is there a way to change the SDK to use gnueabihf ?
>
> In fact, I find it scary that the default toolchain is not armhf. What is the reason behind that ?
> Is it because of the video (GPU/VPU) driver ?
What makes you think it's not HF already? (hint - the hf is
part of the CPU model cortexa9hf)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-08-13 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 12:02 yocto SDK for imx6 sabrelite board. (armel vs armhf) ssinfod ssinfod
2014-08-13 14:15 ` ss infod
2014-08-13 14:22 ` Gary Thomas [this message]
2014-08-13 14:41 ` David Chirgwin
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=53EB74A0.3050804@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.