From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/4] base.bbclass: Add compatibility package name mapping handler
Date: Wed, 27 Jul 2011 16:13:47 +0100 [thread overview]
Message-ID: <1311779631.30326.366.camel@phil-desktop> (raw)
In-Reply-To: <EF599739-F511-4465-B5BD-B19F15534482@dominion.thruhere.net>
On Wed, 2011-07-27 at 17:06 +0200, Koen Kooi wrote:
> From the conversations I had with ARM they implied that it isn't optional for cortex a8/9/15, only neon is (e.g. marvell dove, nvidia tegra2). I haven't seen any black on white contracts saying that, though :)
The spec on the web seems to say fairly clearly that it's optional, at
least in theory. I guess they might have commercial reasons for not
wanting to sell it without VFP in any given situation.
See:
http://www.arm.com/products/processors/cortex-a/cortex-a5.php?tab=Specifications
for example
p.
next prev parent reply other threads:[~2011-07-27 15:18 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
2011-07-27 15:06 ` Koen Kooi
2011-07-27 15:13 ` Phil Blundell [this message]
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=1311779631.30326.366.camel@phil-desktop \
--to=philb@gnu.org \
--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