linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	linux-mips@vger.kernel.org
Subject: Re: MIPS Hardware support
Date: Thu, 27 Feb 2020 23:37:07 +0800	[thread overview]
Message-ID: <2FD88A63-1873-469F-9AF9-27FCB803E839@flygoat.com> (raw)
In-Reply-To: <20200227144910.GA25011@alpha.franken.de>



于 2020年2月27日 GMT+08:00 下午10:49:10, Thomas Bogendoerfer <tsbogend@alpha.franken.de> 写到:
>Hi,
>
>we have 47 MIPS system types and I'd like to get an overview how alive
>they really are. I've already grouped the 47 systems a little bit by
>hardware I already own and regulary test kernels. Could you please
>give me some feedback about the "unclassified" systems ? What systems
>are supported by qemu (real test not just repeating qemu docs) ?
>Thank you for your help.
>
>Thomas.
>
>Hardware I own and regulary boot current kernels:
>
>Jazz family of machines (MACH_JAZZ)	/* runs with qemu */
>SGI IP22 (Indy/Indigo2) (SGI_IP22)
>SGI IP27 (Origin200/2000) (SGI_IP27)
>SGI IP28 (Indigo2 R10k) (SGI_IP28)
>SGI IP30 (Octane/Octane2) (SGI_IP30) 
>SGI IP32 (O2) (SGI_IP32)
>SNI RM200/300/400 (SNI_RM)
>
>Hardware I own, but not booted for a while:
>
>Texas Instruments AR7 (AR7)
>Cobalt Server (MIPS_COBALT)
>DECstations (MACH_DECSTATION)
>Lantiq based platforms (LANTIQ)
>Ralink based machines (RALINK)
>Sibyte BCM91480B-BigSur (SIBYTE_BIGSUR)
>
>Unclassified:
>
>Generic board-agnostic MIPS kernel (MIPS_GENERIC)
>Alchemy processor based machines (MIPS_ALCHEMY)
>Atheros AR231x/AR531x SoC support (ATH25)
>Atheros AR71XX/AR724X/AR913X based boards (ATH79)
>Broadcom Generic BMIPS kernel (BMIPS_GENERIC)
>Broadcom BCM47XX based boards (BCM47XX)
>Broadcom BCM63XX based boards (BCM63XX)
>Ingenic SoC based machines (MACH_INGENIC)
Ingeic X1000 now boots thanks to Yanjie's effort.
I owned a board given by Yanjie, and sometimes test MIPS32 functions on it.

>LASAT Networks platforms (LASAT)
>Loongson 32-bit family of machines (MACH_LOONGSON32)
I owned a Loongson 1C board, and can confirm 5.4 is still bootable.

>Loongson-2E/F family of machines (MACH_LOONGSON2EF)
QEMU Fuloong-2E works fine, tested last year.
And I owned Fuloong-2F. Just tested 5.5 recently.

>Loongson 64-bit family of machines (MACH_LOONGSON64)
No QEMU available.
I owned a Loongson-3B1500 with RS780E PCH system. 
It works well with yesterday's mips-next.

I also have Loongson-3A4000 + 7A system,
which should belongs to this type.
However, Loongson-7A PCH support is still missing in mainline
and I'm going to work on that.

>IMG Pistachio SoC based boards (MACH_PISTACHIO)
>MIPS Malta board (MIPS_MALTA)
I use QEMU Malta for regular tests.
It works smoothly.

>Microchip PIC32 Family (MACH_PIC32)
>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)
>Sibyte BCM91120C-CRhine (SIBYTE_CRHINE)
>Sibyte BCM91120x-Carmel (SIBYTE_CARMEL)
>Sibyte BCM91125C-CRhone (SIBYTE_CRHONE)
>Sibyte BCM91125E-Rhone (SIBYTE_RHONE)
>Sibyte BCM91250A-SWARM (SIBYTE_SWARM)
>Sibyte BCM91250C2-LittleSur (SIBYTE_LITTLESUR)
>Sibyte BCM91250E-Sentosa (SIBYTE_SENTOSA)
>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)
>Para-Virtualized guest system (MIPS_PARAVIRT)

-- 
Jiaxun Yang

  parent reply	other threads:[~2020-02-27 15:38 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 [this message]
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
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=2FD88A63-1873-469F-9AF9-27FCB803E839@flygoat.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=linux-mips@vger.kernel.org \
    --cc=tsbogend@alpha.franken.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).