From: Joshua Kinard <kumba@gentoo.org>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] Reducing the number of the MIPS supported stages
Date: Mon, 05 May 2014 20:15:08 -0400 [thread overview]
Message-ID: <5368298C.2050703@gentoo.org> (raw)
In-Reply-To: <CAEdQ38GLOTA85huVhhHRSqMvwXctrNo+9quKpjQJcNxwzvg5gQ@mail.gmail.com>
On 05/05/2014 19:30, Matt Turner wrote:
> On Mon, May 5, 2014 at 3:02 PM, Joshua Kinard <kumba@gentoo.org> wrote:
>> And I don't see a point in doing an R10K-specific mips4 build. The standard
>> mips4 build is good enough, and users of R10K systems can rebuild to gain
>> the R10K enhancements if needed.
>
> That's not true, as far as I'm aware. glibc for instance has
> compile-time work-arounds for R10k errata. Hangs result without the
> fix.
Ah, that bug. Been a while indeed. My R10K IP28 is in the closet and R10K
O2, last time I tried a kernel, hated me rather fantastically.
The Octane, on the other hand, partially boots now in 3.14.1. At least, I
can get to a working Odyssey console w/ SCSI, keyboard, and even the mouse
looks to work. Still fighting the IOC3 over RTC interrupts, and SCSI is
abysmally slow (too many interrupts, I think -- ~4MB/sec r/w). But it works
again. No serial, RAD1, Impact or SMP yet.
When I fix a few more things, I'll probably attempt to bootstrap a new
userland on it. Current one is from 2009. So, when that happens, I'll be
able to re-verify glibc and the R10k thing again, I guess.
--
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
4096R/D25D95E3 2011-03-28
"The past tempts us, the present confuses us, the future frightens us. And
our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
next prev parent reply other threads:[~2014-05-06 0:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 14:06 [gentoo-mips] Reducing the number of the MIPS supported stages Markos Chandras
2014-05-05 17:04 ` Panagiotis Christopoulos
2014-05-05 17:17 ` Markos Chandras
2014-05-05 17:13 ` Justin Cormack
2014-05-05 17:16 ` Markos Chandras
2014-05-05 17:22 ` Matt Turner
2014-05-05 17:29 ` Markos Chandras
2014-05-05 23:34 ` Matt Turner
2014-05-05 22:02 ` Joshua Kinard
2014-05-05 23:30 ` Matt Turner
2014-05-06 0:15 ` Joshua Kinard [this message]
2014-05-05 23:36 ` Matt Turner
2014-05-06 0:09 ` Joshua Kinard
2014-05-06 7:07 ` Markos Chandras
2014-05-06 8:10 ` Joshua Kinard
2014-05-06 17:50 ` Markos Chandras
2014-05-06 21:37 ` Joshua Kinard
2014-05-07 7:06 ` Markos Chandras
2014-05-07 7:22 ` Joshua Kinard
2014-05-06 11:32 ` Anthony G. Basile
2014-05-06 17:40 ` Markos Chandras
2014-05-05 19:19 ` [gentoo-mips] " Anthony G. Basile
2014-05-05 19:33 ` Markos Chandras
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=5368298C.2050703@gentoo.org \
--to=kumba@gentoo.org \
--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