From: Mark Hatle <mark.hatle@windriver.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] tune-cortexa5.inc: Allow tuning for vfpv3d16, vfpv3 and neon-vfpv4
Date: Thu, 12 Nov 2015 13:11:56 -0600 [thread overview]
Message-ID: <5644E47C.70904@windriver.com> (raw)
In-Reply-To: <20151112184340.GE4230@piout.net>
On 11/12/15 12:43 PM, Alexandre Belloni wrote:
> On 12/11/2015 at 12:26:57 -0600, Mark Hatle wrote :
>> Seems odd to me that the package arch are the same between the generic (assumed
>> to be the default ARMv7a, which is USUALLY VFPv4-D32 in most cases.)
>>
>> If we want to limit to v3 and/or D16. It might make sense for a different
>> package arch, otherwise there is no way to separate the feeds in a
>> multiple-machine configuration with different per-target optimizations.
>>
>> (similarly the -neon versions as well, but that is existing code)
>>
>
> Yeah, I'm also not sure this is the correct thing but all the package
> arch for tune-armv7a* are armv7a so I've replicated that.
>
> Also, I just realized there are no users for armv7a*-vfpv3* in oe-core,
> maybe I should leave those tunes in my soc specific BSP layer?
>
There are a lot of tunes defined that have no direct oe-core users. We try to
define things we think are useful and supported by the included toolchain.
External BSPs may be required to actually test it.
--Mark
next prev parent reply other threads:[~2015-11-12 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 18:06 [PATCH] tune-cortexa5.inc: Allow tuning for vfpv3d16, vfpv3 and neon-vfpv4 Alexandre Belloni
2015-11-12 18:26 ` Mark Hatle
2015-11-12 18:43 ` Alexandre Belloni
2015-11-12 19:11 ` Mark Hatle [this message]
2015-11-12 19:15 ` Martin Jansa
2015-11-13 9:33 ` Alexandre Belloni
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=5644E47C.70904@windriver.com \
--to=mark.hatle@windriver.com \
--cc=alexandre.belloni@free-electrons.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 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.