Openembedded Core Discussions
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: Lukasz Majewski <lukma@denx.de>
Cc: Wolfgang Denk <wd@denx.de>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [thud][PATCH] ppce500v2: remove spe *The PowerPC SPE support is split off to a separate powerpcspe port
Date: Fri, 16 Nov 2018 12:45:56 +0000	[thread overview]
Message-ID: <79fd2ed2fc241bf2770b4e471d94cb024c313140.camel@linuxfoundation.org> (raw)
In-Reply-To: <20181116133124.14279e76@jawa>

On Fri, 2018-11-16 at 13:31 +0100, Lukasz Majewski wrote:
> Hi Richard,
> 
> > What does "The PowerPC SPE support is split off to a separate
> > powerpcspe port" mean? 
> > 
> > That gcc support is being dropped and its going somewhere
> > separate? 
> > 
> > That we're dropping spe support from OE?
> 
> I do hope NOT.
> 
> There are still some users of those SPE SoCs. Please do not remove it
> from OE.

I would highlight that Yocto Project and OE get very little support for
anything PowerPC related and that upstream gcc have already removed
parts of the SPE support. We will likely end up having to follow what
gcc does, we have a hack in place now but it won't last another gcc
major version upgrade.

So if you or your customers care about SPE or PowerPC in general, we
really need to see more support at the Yocto Project advisory board to
continue to keep it as a first class citizen.

Cheers,

Richard




  reply	other threads:[~2018-11-16 12:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16  3:40 [thud][PATCH] ppce500v2: remove spe *The PowerPC SPE support is split off to a separate powerpcspe port C.r. Guo
2018-11-16 11:54 ` Richard Purdie
2018-11-16 12:31   ` Lukasz Majewski
2018-11-16 12:45     ` richard.purdie [this message]
2018-11-19  9:56       ` C.r. Guo
2018-11-19 10:23         ` Lukasz Majewski

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=79fd2ed2fc241bf2770b4e471d94cb024c313140.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=lukma@denx.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=wd@denx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox