From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: armhf support in OpenEmbedded?
Date: Mon, 6 Feb 2012 15:17:26 -0600 [thread overview]
Message-ID: <4F304366.8060201@windriver.com> (raw)
In-Reply-To: <CAMvUbCz0Lts7dUOWWvJeivm9nUb3nuhEqS-QY4+nOYOgmDzEkw@mail.gmail.com>
In oe-core, there are definitions for various tunings that use the ARM EABI w/
HF extension.
The following tunings support that mode: (And armhf is avsolutely not required
to be for the armv7-a CPU.. it compatible with any CPU that supports VFP
instructions... note there are armv7-a systems that do -not- have VFP support,
so these ABI extensions will not work there!)
armv5ehf-vfp armv5tehf-vfp
armv5ehfb-vfp armv5tehfb-vfp
armv5hf-vfp armv5thf-vfp
armv5hfb-vfp armv5thfb-vfp
armv6hf armv6thf
armv6hfb armv6thfb
armv7hf armv7thf armv7hf-neon armv7thf-neon
armv7ahfb armv7athfb armv7ahfb-neon armv7athfb-neon
armv7hf armv7thf armv7hf-neon armv7thf-neon
armv7hfb armv7thfb armv7hfb-neon armv7thfb-neon
See conf/machine/include/arm/*
--Mark
On 2/6/12 3:01 PM, Leon Woestenberg wrote:
> Hello,
>
> do we already have support for the ARM "armhf" ABI in OpenEmbedded? (A quick
> search on the ML didn't get me hits).
>
> Basically,"armhf" is built with -mfloat-abi=hard, and tuned for armv7-a CPUs.
>
>
> http://wiki.debian.org/ArmHardFloatPort
> http://www.powerdeveloper.org/forums/viewtopic.php?p=13645#13645
>
> Regards,
>
> Leon.
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2012-02-06 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 21:01 armhf support in OpenEmbedded? Leon Woestenberg
2012-02-06 21:17 ` Mark Hatle [this message]
2012-02-06 21:17 ` Koen Kooi
2012-02-06 21:22 ` Mark Hatle
2012-02-06 21:40 ` Leon Woestenberg
2012-02-07 7:49 ` Koen Kooi
2012-02-06 22:44 ` Philip Balister
2012-02-06 21:21 ` Phil Blundell
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=4F304366.8060201@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox