From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@oss.sgi.com
Subject: Re: R4600SC Indy
Date: Thu, 15 Aug 2002 13:31:21 +0200 [thread overview]
Message-ID: <20020815113121.GV19435@lug-owl.de> (raw)
In-Reply-To: <20020815020642.A23230@marmot.cita.utoronto.ca>
[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]
On Thu, 2002-08-15 02:06:42 -0400, Robin Humble <rjh@cita.utoronto.ca>
wrote in message <20020815020642.A23230@marmot.cita.utoronto.ca>:
> On Tue, Aug 06, 2002 at 11:19:59AM -0400, Robin Humble wrote:
> >I have an R4600SC Indy and an R5000 Indy and the R4600SC hasn't worked
> >with a kernel since around 2.4.17 13feb2002.
>
> To be precise, the changes that were checked in on 6-mar-2002 broke
> R4600SC support. These changes were to arch/mips/mm/c-r4k.c (and its mips64
> counterpart). The patch below (to 13-aug-02 linux_2_4 CVS) is simply a
> reversal of the changes made on 6-mar-02 and makes my R4600SC Indy work
> just fine.
They broke R4600 Version 1.7 to be exactly, as this CPU has got some
bugs in it's cache flush commands. The result is: you need to disable
interrupts to get the desired result, but that's some kind of PITA
performance-wise, so the workaround for R4k6 V1.7 was dropped later on.
I've got a somewhat better patch introducing all needed routines for the
buggy R4k6 V1.7 and setting them up (more or less correctly).
However, it seems that I did bug somewhere. My patch seems to not be as
stable as expected. I tried to post it at the weekend, but it didn't
show up (size?). I'll try it again these days, though.
MfG, JBG
--
Jan-Benedict Glaw . jbglaw@lug-owl.de . +49-172-7608481
-- New APT-Proxy written in shell script --
http://lug-owl.de/~jbglaw/software/ap2/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2002-08-15 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 15:20 R4600SC Indy Robin Humble
2002-08-06 16:33 ` Florian Lohoff
2002-08-15 6:06 ` Robin Humble
2002-08-15 11:31 ` Jan-Benedict Glaw [this message]
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=20020815113121.GV19435@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-mips@oss.sgi.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