All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: ppc e500v2 support?
Date: Wed, 03 Nov 2010 11:49:51 -0400	[thread overview]
Message-ID: <4CD1849F.6010303@windriver.com> (raw)
In-Reply-To: <AANLkTi=+SkeQJbAvCcmzk20XzY-2Wk9rnypte59Lnkxs@mail.gmail.com>

On 10-11-03 11:34 AM, Frans Meulenbroeks wrote:
> Hi,
>
> 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 =

I can definitely guarantee that this would work in
the yocto kernel (with a small local step for you), in
fact, I've got a full BSP for this, and any of the extra
features in the kernel (SPE, IEEE float, lttng, etc) will
all work for any e500* board.

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.

Cheers,

Bruce

> "calamari"). but gcc-cross-initial fails in do_compile when it tries
> to run configure for the libgcc subdir.
> The problem is similar to http://patchwork.openembedded.org/patch/2026/
>
> Basically gcc-cross-initial fails building libgcc, config.log has:
> cc1: error: not configured for ABI: 'spe'
>
> I feel this is related to the generation of the host triplet.
> OE has conf/distro/include/sane-toolchain.inc which has a func
> compute_os_portion_of_target_triplet
> this one adds gnuspe to the host triplet (and maybe some other things).
>
> poky does not give me that part of the triplet.
>
> Anyone an idea what is wrong (I can provide machine description etc,
> but it is also all in the OE git).
>
> Best regards, Frans
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.pokylinux.org/listinfo/yocto



  parent reply	other threads:[~2010-11-03 15:49 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 [this message]
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
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=4CD1849F.6010303@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=fransmeulenbroeks@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.