From: Mark Hatle <mark.hatle@windriver.com>
To: yocto@yoctoproject.org
Subject: Re: ppc e500v2 support?
Date: Thu, 04 Nov 2010 12:20:33 -0500 [thread overview]
Message-ID: <4CD2EB61.2090502@windriver.com> (raw)
In-Reply-To: <AANLkTinsewJh-==QbQ-LbXmNEZMSdqCKKpf-c8yi=m-a@mail.gmail.com>
On 11/4/10 8:53 AM, Leon Woestenberg wrote:
> Hello Bruce,
>
> On Wed, Nov 3, 2010 at 4:49 PM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>> On 10-11-03 11:34 AM, Frans Meulenbroeks wrote:
>>>
>>> I'm trying to add my powerpc board to yocto (as a test). This board
>>> mpc8536ds has an e500v2 core. It works under OE (MACHINE =
>>
>> When doing the initial freescale board work, I ran into
>> similar (same) problems with userspace (and gcc), and
>> ended up backing off to a more generic optimization level
>> to get things working. So there are a definitely few things
>> to do. I was experimenting with FPU settings, but haven't
>> gone back to look again.
>>
> Was combo did you see problems with?
>
> I added e500v2 support to OpenEmbedded more than one year ago and have
> not seen issues yet in userspace GCC.
> Recently been playing with SPE which also ran fine:
> http://www.sidebranch.nl/spe-apu
>
> Regards,
I'm not sure we have all of the pieces in place yet in the toolchain.
My quick looking of my own e500v1 & e500v2 support includes both libc patches
and compiler patches.
Just an FYI.. the compiler flags for e500v1:
-mcpu=8540 -mfloat-gprs=single -mspe=yes -mabi=spe
and for e500v2:
-mcpu=8548 -mfloat-gprs=double -mspe=yes -mabi=spe
Neither of those would be compatible with the existing "ppc" packaging arch. We
will need to generate at least one new packaging arch type, likely 2 (one for
each). Maybe called ppc_spe or something similar?
The key thing is that each of these cpu's has not only additional SPE
instructions, but also additional registers, specific to those instructions, to
pass values from function to function. It's not just using the PPC soft-float ABI..
--Mark
next prev parent reply other threads:[~2010-11-04 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 15:34 ppc e500v2 support? Frans Meulenbroeks
2010-11-03 15:40 ` Mark Hatle
2010-11-03 15:49 ` Bruce Ashfield
2010-11-03 19:32 ` Frans Meulenbroeks
2010-11-03 21:36 ` Bruce Ashfield
2010-11-04 13:53 ` Leon Woestenberg
2010-11-04 14:29 ` Bruce Ashfield
2010-11-04 17:20 ` Mark Hatle [this message]
2010-11-04 18:02 ` Leon Woestenberg
2010-11-04 18:18 ` Mark Hatle
2010-11-04 18:43 ` Leon Woestenberg
2010-11-04 18:50 ` Mark Hatle
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=4CD2EB61.2090502@windriver.com \
--to=mark.hatle@windriver.com \
--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.