linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: linux-mips@vger.kernel.org
Subject: Re: MIPS Hardware support
Date: Wed, 11 Mar 2020 12:07:54 +0100	[thread overview]
Message-ID: <20200311110754.GA10734@alpha.franken.de> (raw)
In-Reply-To: <20200227144910.GA25011@alpha.franken.de>

On Thu, Feb 27, 2020 at 03:49:10PM +0100, Thomas Bogendoerfer wrote:
> [..]

Thank you everybody for giving me information about your hardware.

So we have following system types without users:

LASAT Networks platforms (LASAT)
IMG Pistachio SoC based boards (MACH_PISTACHIO)
NEC EMMA2RH Mark-eins board (NEC_MARKEINS)
NEC VR4100 series based machines (MACH_VR41XX)
NXP STB220 board (NXP_STB220)
NXP 225 board (NXP_STB225)
PMC-Sierra MSP chipsets (PMC_MSP)
Toshiba TX39 series based machines (MACH_TX39XX)
Toshiba TX49 series based machines (MACH_TX49XX)
Mikrotik RB532 boards (MIKROTIK_RB532)
Cavium Networks Octeon SoC based boards (CAVIUM_OCTEON_SOC)
Netlogic XLR/XLS based systems (NLM_XLR_BOARD)
Netlogic XLP based systems (NLM_XLP_BOARD)

As you might have guessed already I'm thinking about dropping dead platforms.

Looking at git history these are my candicates for dropping in 5.8:

LASAT Networks platforms (LASAT)
NEC EMMA2RH Mark-eins board (NEC_MARKEINS)
PMC-Sierra MSP chipsets (PMC_MSP)

If there are still users of that platforms, please speak up !!!

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  parent reply	other threads:[~2020-03-11 11:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27 14:49 MIPS Hardware support Thomas Bogendoerfer
2020-02-27 15:05 ` Oleksij Rempel
2020-02-27 15:37 ` Jiaxun Yang
2020-02-27 15:43 ` Zhou Yanjie
2020-02-27 15:43 ` YunQiang Su
2020-02-27 16:34 ` Mauro Condarelli
2020-02-27 21:16 ` Maciej W. Rozycki
2020-02-28  7:07 ` Tiezhu Yang
2020-03-01  6:39 ` WANG Xuerui
2020-03-01 15:19   ` Cye Borg
2020-03-01 23:50 ` Joshua Kinard
2020-03-02  8:22   ` Manuel Lauss
2020-03-02 11:11     ` YunQiang Su
2020-03-02  8:35 ` dtb .
2020-03-04 16:22   ` Thomas Bogendoerfer
2020-03-09 11:43     ` Huacai Chen
2020-03-02 14:30 ` Jonas Gorski
2020-03-11 11:07 ` Thomas Bogendoerfer [this message]
2020-03-11 11:13   ` YunQiang Su
2020-03-11 13:46     ` Thomas Bogendoerfer
2021-01-06 19:31 ` Hauke Mehrtens

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=20200311110754.GA10734@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-mips@vger.kernel.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).