linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>, cbe-oss-dev@ozlabs.org
Subject: Re: [Cbe-oss-dev] Cell and new CPU feature bits
Date: Fri, 26 May 2006 16:22:43 +1000	[thread overview]
Message-ID: <1148624563.8089.96.camel@localhost.localdomain> (raw)
In-Reply-To: <200605191211.18737.arnd@arndb.de>

On Fri, 2006-05-19 at 12:11 +0200, Arnd Bergmann wrote:
> On Friday 19 May 2006 06:07, Benjamin Herrenschmidt wrote:
> >  - Extended implementation of dcbt. (Another bit ? Or sould we just have
> > a "CELL" bit ? In which case should it cover the altivec additions too
> > or are those likely to exist in future non-Cell processors ?)
> 
> Isn't that already covered by PPC_FEATURE_CELL? Git log shows

Not specific to cell, 970 at least has it too.

Ben.

      parent reply	other threads:[~2006-05-26  6:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19  4:07 Cell and new CPU feature bits Benjamin Herrenschmidt
2006-05-19  5:19 ` Olof Johansson
2006-05-19  5:27   ` [Cbe-oss-dev] " Andrew Pinski
2006-05-19  7:49     ` Segher Boessenkool
2006-05-26  6:19     ` Benjamin Herrenschmidt
2006-05-26  6:19   ` Benjamin Herrenschmidt
2006-05-26  6:43     ` Olof Johansson
2006-05-26  7:33       ` Benjamin Herrenschmidt
2006-05-26 15:16         ` Olof Johansson
2006-05-19  8:16 ` Gabriel Paubert
2006-05-22 19:46   ` [Cbe-oss-dev] " Alex Rosenberg
2006-05-23 21:52     ` Benjamin Herrenschmidt
2006-05-26  6:22   ` Benjamin Herrenschmidt
2006-05-19 10:11 ` [Cbe-oss-dev] " Arnd Bergmann
2006-05-19 16:18   ` Olof Johansson
2006-05-19 22:33     ` Paul Mackerras
2006-05-26  6:22   ` Benjamin Herrenschmidt [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=1148624563.8089.96.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=arnd@arndb.de \
    --cc=cbe-oss-dev@ozlabs.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).