All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Leon Woestenberg <leon.woestenberg@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: ppc e500v2 support?
Date: Thu, 04 Nov 2010 10:29:46 -0400	[thread overview]
Message-ID: <4CD2C35A.1050807@windriver.com> (raw)
In-Reply-To: <AANLkTinsewJh-==QbQ-LbXmNEZMSdqCKKpf-c8yi=m-a@mail.gmail.com>

On 10-11-04 09: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?

It was particular to the mpc8315e config.

>
> 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

Runtime on the target is fine, since this is all well known
and working (we've had SPE/e500/e500v2 BSPs working for
quite some time), the issue was specific to -Os and gcc 4.5
bootstrap building.

These have all largely been resolved now, and a minor kernel
patch has the powerpc kernel boot code building and working,
and cleanups can happen in our post yocto 0.9 efforts.

Cheers,

Bruce

>
> Regards,



  reply	other threads:[~2010-11-04 14:29 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 [this message]
2010-11-04 17:20     ` Mark Hatle
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=4CD2C35A.1050807@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=leon.woestenberg@gmail.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.