All of lore.kernel.org
 help / color / mirror / Atom feed
From: YunQiang Su <wzssyqa@gmail.com>
To: Manuel Lauss <manuel.lauss@gmail.com>
Cc: Linux-MIPS <linux-mips@vger.kernel.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Joshua Kinard <kumba@gentoo.org>
Subject: Re: MIPS Hardware support
Date: Mon, 2 Mar 2020 19:11:53 +0800	[thread overview]
Message-ID: <CAKcpw6XitkcBX5TJcqPWVt6mVpcrgvFZ7UCZztagTtsxAQoHvQ@mail.gmail.com> (raw)
In-Reply-To: <CAOLZvyGyjksZWMwFwbTW=WOobnsPQXh-BTU7DReWjBbGxSpF5A@mail.gmail.com>

Manuel Lauss <manuel.lauss@gmail.com> 于2020年3月2日周一 下午4:22写道：
>
> On Mon, Mar 2, 2020 at 12:50 AM Joshua Kinard <kumba@gentoo.org> wrote:
> >
> > On 2/27/2020 09:49, Thomas Bogendoerfer wrote:
> > > 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.
>
> I have all Alchemy DB1xxx boards, still working, as well as few MTX-1.
>
> As an aside, does anyone know where to get "newer" MIPS hardware,

Loongson has 64r5 machines.
Ingenic has 32r2+ machines
elvse has 32r5 boards with P5600: http://elveesneotek.com/index.php?id=1575

> for example with 64bit MipsR6 cores?

You cannot purchase r6 machines yet.
Currently we can only use qemu:
   http://mips64el.bfsu.edu.cn/debian-new/tarball/sid/qemu/

>
> Manuel



-- 
YunQiang Su

  reply	other threads:[~2020-03-02 11:12 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 [this message]
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=CAKcpw6XitkcBX5TJcqPWVt6mVpcrgvFZ7UCZztagTtsxAQoHvQ@mail.gmail.com \
    --to=wzssyqa@gmail.com \
    --cc=kumba@gentoo.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=manuel.lauss@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.