From: Michael Ellerman <michael@ellerman.id.au>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linuxppc-dev@ozlabs.org, Carlos Eduardo Seo <eduseo@br.ibm.com>
Subject: Re: [PATCH] add Altivec/VMX state to coredumps
Date: Thu, 27 Sep 2007 12:53:56 +1000 [thread overview]
Message-ID: <1190861636.6502.13.camel@concordia> (raw)
In-Reply-To: <Pine.LNX.4.62.0709260937540.6243@pademelon.sonytel.be>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
On Wed, 2007-09-26 at 09:42 +0200, Geert Uytterhoeven wrote:
> On Wed, 26 Sep 2007, Kumar Gala wrote:
> > On Sep 25, 2007, at 11:56 PM, Mark Nelson wrote:
> > > What cores have SPE at the moment? Also, perhaps more importantly,
> > > are there any plans to have Altivec and SPE in the same core?
> >
> > The e500 cores's from Freescale.
> >
> > No, they are pretty much mutually exclusive.
>
> Bummer, only now do I realize this thread is not about the Synergistic
> Processing Elements but about the Signal Processing Extension...
Yeah, it's a bit of a downer. Luckily most of the Cell kernel code uses
SPU rather than SPE.
Happily it looks like SPU will become ambiguous if Niagara II support
lands in the kernel:
http://realworldtech.com/page.cfm?ArticleID=RWT090406012516&p=2
sigh :)
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-09-27 2:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 4:03 [PATCH] add Altivec/VMX state to coredumps Mark Nelson
2007-09-25 12:39 ` Kumar Gala
2007-09-25 18:00 ` Matt Sealey
2007-09-25 22:18 ` Benjamin Herrenschmidt
2007-09-26 11:05 ` Matt Sealey
2007-09-26 13:21 ` Segher Boessenkool
2007-09-26 13:32 ` Kumar Gala
2007-09-26 13:38 ` Segher Boessenkool
2007-09-26 14:00 ` Matt Sealey
2007-09-26 1:22 ` Mark Nelson
2007-09-26 3:56 ` Kumar Gala
2007-09-26 4:56 ` Mark Nelson
2007-09-26 5:37 ` Kumar Gala
2007-09-26 7:42 ` Geert Uytterhoeven
2007-09-27 2:53 ` Michael Ellerman [this message]
2007-09-27 2:48 ` Michael Ellerman
2007-09-27 10:10 ` Kumar Gala
2007-09-27 23:54 ` Michael Ellerman
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=1190861636.6502.13.camel@concordia \
--to=michael@ellerman.id.au \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=eduseo@br.ibm.com \
--cc=linuxppc-dev@ozlabs.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.