From: Matt Turner <mattst88@gmail.com>
To: gentoo-mips@lists.gentoo.org
Subject: [gentoo-mips] Re: What kind of MIPS hardware do we have? (Looking to restart Gentoo/MIPS, need info)
Date: Sat, 10 Jul 2010 23:13:04 -0400 [thread overview]
Message-ID: <AANLkTilY4EGiMaezn0xjrJYMM8n6PieUGQ6GL7dMF4pA@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinnjCachIqD3XjzwMO4Zuun788eHR_PwesAktAj@mail.gmail.com>
On Thu, Jul 8, 2010 at 12:22 PM, Matt Turner <mattst88@gmail.com> wrote:
> Hi,
> I'm going to be working on Gentoo/MIPS. I'm planning to provide N32
> stages, and I want to know what kind of MIPS hardware people have to
> run Gentoo. With this info, I should be able to better prioritize the
> tasks.
>
> So please reply with what kind of hardware you've got.
>
> Thanks!
> Matt
Thanks everybody for your responses.
A bit of background: MIPS has 3 ABIs: o32, n32, n64. o32 is the common
denominator, but is pretty inefficient. See [1]. As I suspected, all
the hardware people care about can use the n32 ABI, which is quite a
bit better.
To summarize the hardware collection
- 5 MIPS III/Loongson little-endian STMicroelectronics systems (Lemote, Gdium)
- 11 MIPS IV big-endian SGI systems
- 3 MIPS IV little-endian Cobalt systems
- 2 MIPS64 selectable-endian Broadcom systems
I've got a working n32 big-endian installation, and am preparing an
n32 little-endian installation at the moment. Once these are set up,
I'll start preparing some n32 stages.
I think first priority should be mips4 big-endian. From there, I don't
know whether I should build a mips4-le stage for cobalt systems, or a
mips3-le stage that would work for cobalt and Loongson. Do we know of
any plain MIPS III little-endian hardware?
Also, the MIPS port is going to be pretty unmaintainable until we can
kill off ~mips from ACCEPT_KEYWORDS. Currently, attempting to upgrade
almost anything causes something to break.
What do you guys think?
Thanks,
Matt
[1] http://www.linux-mips.org/wiki/WhatsWrongWithO32N32N64
next prev parent reply other threads:[~2010-07-11 4:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 16:22 [gentoo-mips] What kind of MIPS hardware do we have? (Looking to restart Gentoo/MIPS, need info) Matt Turner
2010-07-08 17:14 ` Vincent-Xavier JUMEL
2010-07-08 17:49 ` Zhang Le
2010-07-08 18:39 ` Michael Schneider
2010-07-08 20:39 ` Michael Loeffler
2010-07-08 21:10 ` Matt Turner
2010-07-08 20:53 ` Mads
2010-07-08 21:49 ` Ed Stafford
2010-07-08 22:19 ` Alexey Shvetsov
2010-07-09 7:17 ` Jens Seidel
2010-07-09 7:30 ` Arianna Arona
2010-07-09 8:08 ` Jason Bergstrom
2010-07-09 8:16 ` Phil Botha
2010-07-09 12:36 ` Karin Willers
2010-07-09 13:56 ` Mark E Mason
2010-07-09 18:48 ` Anthony G. Basile
2010-07-11 3:13 ` Matt Turner [this message]
2010-07-11 11:53 ` [gentoo-mips] " Panagiotis Christopoulos
2010-07-11 14:08 ` Matt Turner
2010-07-12 18:51 ` Mark E Mason
2010-07-21 8:04 ` Manuel Lauss
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=AANLkTilY4EGiMaezn0xjrJYMM8n6PieUGQ6GL7dMF4pA@mail.gmail.com \
--to=mattst88@gmail.com \
--cc=gentoo-mips@lists.gentoo.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