All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: Hard floating point support for armv7a wmmx2 processor in oe-core
Date: Thu, 12 Apr 2012 13:25:18 -0500	[thread overview]
Message-ID: <4F871E0E.7080500@windriver.com> (raw)
In-Reply-To: <CAHTvVMen9K_AGfn8O7GMgKvY0XZ-oiDg3oOmSz_sBK6GSGChtQ@mail.gmail.com>

On 4/12/12 12:38 PM, Nicolas Aguirre wrote:
> Hi,
>
> I'm building an oe-core minimal image and toolchain for the cubox[1]
> which has a Marvell Armada 510 SoC, also known as Dove.
> It's a armv7 Arm processor with wmmx2 instruction set [2].
>
> I setup a new machine for the cubox and added :
> require conf/machine/include/arm/arch-armv7a.inc
> in my cubox.conf file
>
> I also added
> ARM_FP_MODE = "hardfp"
> TARGET_FPU = "hardfp"
> in my local.conf file.

That is not how to enable the mode with the newer tune infrastructure.  You need 
to simply enable a tune, in your machine configuration, that matches the desired 
output.

The following are the defined VFP (hard float requires VFP) tunes for hard float:

armv7ahf armv7athf armv7ahf-neon armv7athf-neon

the "t" varients support thumb, but don't have it enabled by default..

the -neon variants also enabled the neon instructions.

I do not know what the "wmmx2" instructions are, if they are different from VFP 
and Neon, then it sounds like you need a custom tune.

Your machine configure should set DEFAULTTUNE = "..." where "..." is the tune 
you want for that given machine.  (armv7ahf should be a safe place to start.)

> It finished the build sucessfully for angstrom efl-nodm-image.
>
> I don't know exactly which option enable and where to add it to enable
> hard floating point.
> I see in meta-oe/meta/conf/machine/include/arm/arch-armv7a.inc
> references to the armv7ahf architecture but without idea how to
> activate it.
>
> Btw is the 'a' after armv7 important for me ? As it seems that this
> arm core is an armv7 and not armv7a. I dont find arch-armv7.inc file
> in oe-core.

There was a recent commit that seemed to indicate that armv7 don't really exist, 
and everything is an armv7a....  One of the ARM experts will have to help 
clarify that point.

> Another problem is, how to add support for wmmx2 instruction set ?
> There is tune-iwmmxt.inc but it seems to refer to armv5 arch. There is
> a way to enable this instruction set ?

Figure out the correct set of commands for gcc to support this processor, and I 
can help you define a custom tune file.

The few references I found in a quick google search seem to indicate that the 
core does support thumb, it should use the armv7-a compilation, and there is 
little to no support for the wmmx2 instructions.

--Mark

> Any help would be appreciate :)
>
> [1] http://www.solid-run.com/products/cubox
> [2] http://www.marvell.com/application-processors/armada-500/
>
> regards,




  reply	other threads:[~2012-04-12 19:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 17:38 Hard floating point support for armv7a wmmx2 processor in oe-core Nicolas Aguirre
2012-04-12 18:25 ` Mark Hatle [this message]
2012-04-18 10:29   ` Nicolas Aguirre
2012-04-29  2:50     ` Khem Raj
2012-04-12 19:43 ` Andrei Gherzan
2012-04-12 19:50 ` Koen Kooi

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=4F871E0E.7080500@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-devel@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 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.