All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: yocto@yoctoproject.org
Subject: Re: TARGET_FPU for mpc8315e-rdb listed as SPE??
Date: Wed, 10 Nov 2010 08:58:08 -0500	[thread overview]
Message-ID: <4CDAA4F0.1060802@windriver.com> (raw)
In-Reply-To: <4CDAA03C.8090004@windriver.com>

On 10-11-10 08:38 AM, Bruce Ashfield wrote:
> On 10-11-10 01:46 AM, Kumar Gala wrote:
>> Why does the meta/conf/machine/mpc8315e-rdb.conf list TARGET_FPU as
>> SPE. This isn't correct for an MPC8313 SoC.
>
> It isn't used at the moment, so we can safely
> ignore this.
>
> It was a hold over from when I initially created
> the BSP, and I've since changed it locally, but
> haven't sent the updated BSP yet.

To clarify on this point, the kernel configuration
is NOT using SPE for this, and I was attempting to
use the FPU setting to trigger some different gcc
flags during development the base of that test was
an e500 board, so the SPE setting leaked in, but is
unused.

At the moment, it is actually using soft-float, and
I had planned to submit a change to clarify that.

If there's another option, let me know and I'll
rebase my patches and change it again.

Cheers,

Bruce

>
> Cheers,
>
> Bruce
>
>>
>> - k
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>



  reply	other threads:[~2010-11-10 13:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10  6:46 TARGET_FPU for mpc8315e-rdb listed as SPE?? Kumar Gala
2010-11-10 13:25 ` Richard Purdie
2010-11-10 13:38 ` Bruce Ashfield
2010-11-10 13:58   ` Bruce Ashfield [this message]
2010-11-10 14:11     ` Kumar Gala
2010-11-10 14:23       ` Bruce Ashfield
2010-11-10 15:03         ` Kumar Gala
2010-11-10 15:07           ` Bruce Ashfield

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=4CDAA4F0.1060802@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=galak@kernel.crashing.org \
    --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.