linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: Marc Dietrich <marvin24@gmx.de>, Geoff Levand <geoff@infradead.org>
Subject: Re: Time to remove platforms/cell?
Date: Thu, 17 Sep 2015 11:31:21 +0200	[thread overview]
Message-ID: <7144823.dIR0EDXkmx@wuerfel> (raw)
In-Reply-To: <2023345.Irprl084gX@fb07-iapwap2>

On Thursday 17 September 2015 10:43:39 Marc Dietrich wrote:
> Am Donnerstag, 17. September 2015, 15:28:47 schrieb Michael Ellerman:
> > Discuss ...
> 
> as long as Geoff still maintains the ps3 port - why?
> 
We already removed celleb a while ago, which was arguably the least
commonly used one.

Within platforms/cell, we have three separate portions that we need
to look at:

a) Common ps3/ibm parts: spufs, oprofile
   We should not remove them before we plan to also remove platforms/ps3
   support, which doesn't seem likely in the near term. We can move them
   to platforms/ps3 if we decide to remove the rest.

b) Support for IBM blades:
   It is unlikely that there are QS20 blades still around and being used
   at all, but there is very little code specific to them.
   For QS21/QS22, there are probably still a few in existence, but
   I have no idea whether anybody would consider running a 4.x kernel
   on them. There are also some customer-specific Cell machines that
   are vaguely related to QS22 and that are in a similar state.
   I don't mind removing the code, but if anybody is still using it
   on new kernels, we should be prepared to put it back.

c) QPACE. We know who the three users were, and they have upgraded to
   QPACE2 (based on Intel Xeon Phi) this year. Removing this would be
   appreciated as it lets us clean up one of the ugly corners of the
   8250 uart driver.

	Arnd

  reply	other threads:[~2015-09-17  9:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17  5:28 Time to remove platforms/cell? Michael Ellerman
2015-09-17  8:43 ` Marc Dietrich
2015-09-17  9:31   ` Arnd Bergmann [this message]
2015-09-17 10:05     ` Michael Ellerman
2015-09-17 11:01       ` Arnd Bergmann
2015-09-17 17:50       ` Geoff Levand
2015-09-17  9:45   ` Michael Ellerman
2015-09-17 10:28     ` Marc Dietrich
2015-09-17 11:15       ` Arnd Bergmann
2015-09-21  9:42         ` Michael Ellerman
2015-09-21  9:44       ` Michael Ellerman
2015-10-04 19:27       ` Geoff Levand
2015-10-05 10:27         ` Marc Dietrich
2015-10-07 17:20           ` Geoff Levand
2015-10-08 18:10             ` Geoff Levand
2015-10-09 17:45               ` Geoff Levand
2015-10-09 21:13                 ` Marc Dietrich
2015-10-22 19:15                   ` Geoff Levand
2015-10-23  1:54                     ` Michael Ellerman
2015-10-23  8:00                       ` Marc Dietrich

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=7144823.dIR0EDXkmx@wuerfel \
    --to=arnd@arndb.de \
    --cc=geoff@infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=marvin24@gmx.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;
as well as URLs for NNTP newsgroup(s).