From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: YunQiang Su <wzssyqa@gmail.com>
Cc: linux-mips <linux-mips@vger.kernel.org>
Subject: Re: MIPS Hardware support
Date: Wed, 11 Mar 2020 14:46:29 +0100 [thread overview]
Message-ID: <20200311134629.GA13742@alpha.franken.de> (raw)
In-Reply-To: <CAKcpw6Uew4e4Qus2Ox0+0RubwbfQQp+37CVKftK8EKYyrwWKsQ@mail.gmail.com>
On Wed, Mar 11, 2020 at 07:13:57PM +0800, YunQiang Su wrote:
> Thomas Bogendoerfer <tsbogend@alpha.franken.de> 于2020年3月11日周三 下午7:08写道：
> >
> > 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:
> >
> > [..]
> > Cavium Networks Octeon SoC based boards (CAVIUM_OCTEON_SOC)
>
> We are using it for our Debian build farm, and they are quite important.
good to know, and if I haven't made it clear enough, I only want to
drop the three listed platforms below.
> > LASAT Networks platforms (LASAT)
> > NEC EMMA2RH Mark-eins board (NEC_MARKEINS)
> > PMC-Sierra MSP chipsets (PMC_MSP)
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2020-03-11 13:53 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
2020-03-11 11:13 ` YunQiang Su
2020-03-11 13:46 ` Thomas Bogendoerfer [this message]
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=20200311134629.GA13742@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-mips@vger.kernel.org \
--cc=wzssyqa@gmail.com \
/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).