All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Seeger <steven.seeger@flightsystems.net>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Greg Gallagher <greg@embeddedgreg.com>,
	"Pirou, Florent" <florent.pirou@intel.com>,
	"Wang, Rick Y" <rick.y.wang@intel.com>,
	"Hu, Mingliang" <mingliang.hu@intel.com>,
	"Xenomai (xenomai@xenomai.org)" <xenomai@xenomai.org>
Subject: Re: initial porting of IPIPE x86_64 patches onto Linux stable 5.4.52
Date: Tue, 25 Aug 2020 10:40:13 -0400	[thread overview]
Message-ID: <1797573.eGJsNajkDb@omoikane> (raw)
In-Reply-To: <20200825132500.4c5z6a3yesfe2wbe@csclub.uwaterloo.ca>

On Tuesday, August 25, 2020 9:25:00 AM EDT Lennart Sorensen wrote:
> A 5020 is an e5500, which is nothing like an e500.  The e500 is PowerpC
> SPE, while the e5500 (and the e300, e500mc and e6500) are "real" PowerPC
> instead with a somewhat different instruction set.

Sorry e500 was a typo in that case.

> GCC 9 even dropped support for the PPC SPE, while PPC is fully supported.
> 

Yeah there are e500 boards being made for military, aerospace, and LEO (low earth orbit) 
uses. There is concern that gcc 9 dropped SPE support, but it's up to vendors to support 
maintenance of it.

> 
> The e500's existence offends me since it fragments the powerpc
> architecture.  Yuck. :)

Well I won't say anything good or bad about it, but it's the one I know the most since it's 
what I work with all the time. ;)

The worst thing I ever had to deal with was making changes to a 603 instruction set 
simulator to make it be a 601. The subtle differences between POWER and PowerPC ISAs 
were quite a pain to find at the time. This was years ago.

But yeah all my work (and tested support with xenomai) have been on a e500v2. (8548)

Steven


      reply	other threads:[~2020-08-25 14:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24  0:48 initial porting of IPIPE x86_64 patches onto Linux stable 5.4.52 Meng, Fino
2020-08-24  6:09 ` Jan Kiszka
2020-08-24 15:02   ` Greg Gallagher
2020-08-24 15:05     ` Steven Seeger
2020-08-25 13:25       ` Lennart Sorensen
2020-08-25 14:40         ` Steven Seeger [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=1797573.eGJsNajkDb@omoikane \
    --to=steven.seeger@flightsystems.net \
    --cc=florent.pirou@intel.com \
    --cc=greg@embeddedgreg.com \
    --cc=jan.kiszka@siemens.com \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=mingliang.hu@intel.com \
    --cc=rick.y.wang@intel.com \
    --cc=xenomai@xenomai.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.