From: Darren Hart <dvhart@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 1/1] beagleboard: enable hard floating point abi
Date: Tue, 23 Aug 2011 06:31:45 -0700 [thread overview]
Message-ID: <4E53ABC1.3050906@linux.intel.com> (raw)
In-Reply-To: <CAD08DEC-FD47-4799-9871-289CA89279FE@dominion.thruhere.net>
On 08/23/2011 05:38 AM, Koen Kooi wrote:
>
> Op 20 aug. 2011, om 00:23 heeft Darren Hart het volgende geschreven:
>
>> Fixes [YOCTO #1203]
>>
>> Using the hard floating point abi is incompatible with some binary
>> libaries and 3D support for the Beagleboard. As we do not provide
>> these in poky and meta-yocto, we can take advantage of the hard
>> floating point abi.
>
> What advantage are you talking about? So far everyone has been unable
> to provide real-world numbers[1] that show hardfp making a difference
> compared to a properly configured softfp. The numbers debian and
> meego are showing are comparing it against completely vfpless builds,
That's good reasoning to stick with softfp+neon. Unfortunately I can't
find the mail threads that first got me looking into adding hardfp
support. As I said, I'm not sold on the idea, but it was requested so I
looked into how to address it.
If nobody comes forward saying they would really like to have this, I'm
going to modify the patch series to disable hardfp by default, but leave
the infrastructure in place so people can enable if they like.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-08-23 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 22:23 [PATCH 0/1] beagleboard: enable hard floating point abi Darren Hart
2011-08-19 22:23 ` [PATCH 1/1] " Darren Hart
2011-08-23 12:32 ` Jason Kridner
2011-08-23 12:38 ` Koen Kooi
2011-08-23 13:31 ` Darren Hart [this message]
2011-08-23 15:34 ` Tom Rini
2011-08-23 16:55 ` Darren Hart
2011-08-23 17:08 ` Tom Rini
2011-08-23 17:11 ` Philip Balister
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=4E53ABC1.3050906@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=yocto@yoctoproject.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.