From: Stuart Longland <stuartl@longlandclan.id.au>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] n64 stages for mipsel… any interest?
Date: Tue, 6 Jun 2017 23:10:51 +1000 [thread overview]
Message-ID: <37a2d370-d989-f878-65ae-311b0b444dd9@longlandclan.id.au> (raw)
In-Reply-To: <48972734-ee5f-c966-b03a-48f134bbcab2@longlandclan.id.au>
On 14/05/17 13:54, Stuart Longland wrote:
> I suspect this will take a fortnight or so… I have contemplating
> resurrecting the old Qube II for this, but it can't compete on RAM, and
> I haven't yet built the binaries with the NOP fix flag for them to run
> on Loongson.
>
> If I get some stages built, is there any interest in the community? I'm
> willing to throw them up somewhere where they can be mirrored (I can
> host here, but my uplink is ~1Mbps) and made accessible to all.
Well, after much compiling with a slow QEMU VM… here's the first batch.
http://www.longlandclan.id.au/~stuartl/gentoo/mips/n64/
I have not yet tried these out, *at all*, this is just the raw output
from Catalyst. I've simply thrown them up here with GnuPG signatures,
and will be trying them out sometime this weekend on my Yeeloong, which
is presently running OpenBSD/loongson.
These *should* work on Loongson 2E/2F, and anything else that is at
least MIPS-III ISA.
I have since found out that they will *NOT* work on MIPS64r6 (i.e. I6400
on QEMU) straight-up: but *should* be able to run on such hardware (this
is not tested yet) if you do the following:
- enable MIPS64r2 emulation by compiling the kernel with
CONFIG_MIPSR2_TO_R6_EMULATOR specifying the `mipsr2emu=1` kernel argument
- specifying the `nofpu=1` kernel argument to use the in-kernel software FPU
Otherwise you'll get the kernel dying with the message runaway loop
modprobe binfmt-464c (ask how I know… thanks to Maciej Rozycki for
guiding me on that). That's another avenue of testing I'll be doing.
As mentioned, if there's interest, I can have a crack at doing some
big-endian ones too for you SGI users out there, although given the
additional memory footprint of n64 over n32 and smaller RAM sizes of
such machines, n32 might be the better target.
Regards,
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
next prev parent reply other threads:[~2017-06-06 13:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 3:54 [gentoo-mips] n64 stages for mipsel… any interest? Stuart Longland
2017-05-14 4:23 ` Joshua Kinard
2017-05-14 5:56 ` Stuart Longland
2017-05-26 7:28 ` Stuart Longland
2017-06-06 13:10 ` Stuart Longland [this message]
2017-06-09 7:15 ` Stuart Longland
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=37a2d370-d989-f878-65ae-311b0b444dd9@longlandclan.id.au \
--to=stuartl@longlandclan.id.au \
--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