Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/4] base.bbclass: Add compatibility package name mapping handler
Date: Wed, 27 Jul 2011 10:04:52 -0500	[thread overview]
Message-ID: <4E302914.7040207@windriver.com> (raw)
In-Reply-To: <1311778937.30326.361.camel@phil-desktop>

On 7/27/11 10:02 AM, Phil Blundell wrote:
> On Wed, 2011-07-27 at 09:44 -0500, Mark Hatle wrote:
>> On 7/27/11 9:29 AM, Richard Purdie wrote:
>>> This means if PKGARCHCOMPAT_ARMV7A is set, "armv7a-vfp-neon" is renamed
>>> to be "armv7a". Other compatibility mappings can be added as needed.
>>
>> There are multiple armv7 cores without neon...  I think there might even be one
>> or two custom cores w/o VFP.  (Yes I know this violates the core spec from ARM,
>> but people do that all of the time.)
> 
> Which spec are you thinking of?  As far as I know, VFP has always been
> optional for both ARM11 and Cortex.

I thought VFP was part of the instruction set as of ARMv7.  Neon is recommended
but options.  As I mentioned though, I know of chips in design that don't have
Neon, and I suspect also don't have VFP -- but they're ARMv7.. (they also have
stripped out the thumb2 part as well..)

--Mark

> p.
> 
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2011-07-27 15:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 14:29 [PATCH 0/4] Various Misc tweaks Richard Purdie
2011-07-27 14:29 ` [PATCH 1/4] base.bbclass: Add compatibility package name mapping handler Richard Purdie
2011-07-27 14:44   ` Mark Hatle
2011-07-27 14:50     ` Richard Purdie
2011-07-27 15:45       ` Koen Kooi
2011-07-27 15:02     ` Phil Blundell
2011-07-27 15:04       ` Mark Hatle [this message]
2011-07-27 15:06       ` Koen Kooi
2011-07-27 15:13         ` Phil Blundell
2011-07-30 18:43           ` Khem Raj
2011-07-30 20:01             ` Phil Blundell
2011-07-27 14:29 ` [PATCH 2/4] gcc: Drop part of the 64bithack patch which is no longer used Richard Purdie
2011-07-28 14:35   ` Lu, Lianhao
2011-07-28 14:55     ` Kumar Gala
2011-08-02 18:28   ` Khem Raj
2011-07-27 14:29 ` [PATCH 3/4] module-init-tools-cross: Drop static binaries patch as a better fix has been merged Richard Purdie
2011-07-27 14:29 ` [PATCH 4/4] base.bbclass: Fix PACKAGE_ARCH typo Richard Purdie
2011-07-30 18:40   ` Khem Raj

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=4E302914.7040207@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