From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@oss.sgi.com
Subject: Re: [Oops] Indy R4600 Oops(es) w/ 2.4.19-rc1
Date: Mon, 1 Jul 2002 19:22:15 +0200 [thread overview]
Message-ID: <20020701172215.GU17216@lug-owl.de> (raw)
In-Reply-To: <Pine.GSO.3.96.1020701185152.7601J-100000@delta.ds2.pg.gda.pl>
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
On Mon, 2002-07-01 19:02:38 +0200, Maciej W. Rozycki <macro@ds2.pg.gda.pl>
wrote in message <Pine.GSO.3.96.1020701185152.7601J-100000@delta.ds2.pg.gda.pl>:
> On Mon, 1 Jul 2002, Jan-Benedict Glaw wrote:
> > I'm not really familiar w/ cache and interrupt handling/masking, and I
> > don't (yet) exactly know how to check for the buggy old R4600, but I
> > think I'll have to become an expert around that:-O
>
> The check is already in place -- see setup_noscache_funcs() in
> arch/mips/mm/c-r4k.c, only the implementation is incomplete which started
> biting after interrupts became active.
Hmmm... I think Ill have to read some heavy MIPS books first:-)
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 --]
next prev parent reply other threads:[~2002-07-01 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-29 22:05 [Oops] Indy R4600 Oops(es) w/ 2.4.19-rc1 Jan-Benedict Glaw
2002-06-30 17:47 ` Jan-Benedict Glaw
2002-07-01 9:13 ` Jan-Benedict Glaw
2002-07-01 9:43 ` Jan-Benedict Glaw
2002-07-01 14:28 ` Maciej W. Rozycki
2002-07-01 15:13 ` Jan-Benedict Glaw
2002-07-01 17:02 ` Maciej W. Rozycki
2002-07-01 17:22 ` Jan-Benedict Glaw [this message]
2002-07-01 17:24 ` Karel van Houten
2002-07-01 17:27 ` Jan-Benedict Glaw
2002-07-01 17:46 ` Maciej W. Rozycki
2002-07-01 15:55 ` Buggy R4600 support (was: [Oops] Indy R4600 Oops(es) w/ 2.4.19-rc1) Jan-Benedict Glaw
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=20020701172215.GU17216@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