All of lore.kernel.org
 help / color / mirror / Atom feed
* yocto SDK for imx6 sabrelite board. (armel vs armhf)
@ 2014-08-12 12:02 ssinfod ssinfod
  2014-08-13 14:15 ` ss infod
  0 siblings, 1 reply; 4+ messages in thread
From: ssinfod ssinfod @ 2014-08-12 12:02 UTC (permalink / raw)
  To: meta-freescale@yoctoproject.org

[-- Attachment #1: Type: text/plain, Size: 945 bytes --]

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 ?

Thanks,
ssinfod

[-- Attachment #2: Type: text/html, Size: 1294 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2014-08-13 14:41 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2014-08-13 14:41     ` David Chirgwin

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.