Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: "C.r. Guo" <chunrong.guo@nxp.com>
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: Mon, 19 Nov 2018 11:23:43 +0100	[thread overview]
Message-ID: <20181119112343.0a90ba2b@jawa> (raw)
In-Reply-To: <DB7PR04MB5068B1F79EED7E9F1531147184D80@DB7PR04MB5068.eurprd04.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2154 bytes --]

On Mon, 19 Nov 2018 09:56:35 +0000
"C.r. Guo" <chunrong.guo@nxp.com> wrote:

> Hello all,
> Please review gcc changes about issue.
> https://www.gnu.org/software/gcc/gcc-8/changes.html
> https://gcc.gnu.org/ml/gcc/2018-04/msg00102.html
> 

Thanks for the info.

Shall I assume that NXP is regarding this port (SPE) as an obsolete one
and do not plan to spent any more resources on it?

> thanks
> chunrong
> 
> 
> 
> 
> 
> -----Original Message-----
> From: richard.purdie@linuxfoundation.org
> <richard.purdie@linuxfoundation.org> Sent: 2018年11月16日 20:46
> To: Lukasz Majewski <lukma@denx.de>
> Cc: C.r. Guo <chunrong.guo@nxp.com>;
> openembedded-core@lists.openembedded.org; Wolfgang Denk <wd@denx.de>
> Subject: Re: [OE-core] [thud][PATCH] ppce500v2: remove spe *The
> PowerPC SPE support is split off to a separate powerpcspe port
> 
> 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
> 
> 




Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 499 bytes --]

      reply	other threads:[~2018-11-19 10:23 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
2018-11-19  9:56       ` C.r. Guo
2018-11-19 10:23         ` Lukasz Majewski [this message]

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=20181119112343.0a90ba2b@jawa \
    --to=lukma@denx.de \
    --cc=chunrong.guo@nxp.com \
    --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