From: "Robert Keller" <rck@corp.home.net>
To: "William J. Earl" <wje@fir.engr.sgi.com>,
"Robert Keller" <rck@corp.home.net>
Cc: Ralf Baechle <ralf@uni-koblenz.de>, linux@cthulhu.engr.sgi.com
Subject: Re: after the kernel seems to live
Date: Wed, 02 Jun 1999 14:32:31 -0700 [thread overview]
Message-ID: <4.1.19990602142531.03e112b0@poptart> (raw)
In-Reply-To: <199906021756.KAA04212@fir.engr.sgi.com>
At 10:56 AM 6/2/99 -0700, William J. Earl wrote:
>Robert Keller writes:
> > At 12:46 AM 5/28/99 +0200, Ralf Baechle wrote:
> > >The R5000 is supported and known to work. You happen to have a
> > >second level cache on that board?
> >
> > how convinced are people that the VR5000 is supported? I'm running
> > the latest code off the linux.sgi.com cvs server and I'm getting *very*
> > weird page faulting problems when doing the kernel/user space
> > hazard shuffle. Its really hard to describe the problems as they are
> > not deterministic: sometimes the right thing happens, other times
> > I get restricted instruction exceptions... Both of these can happen on
> > the very same kernel binary...
>
> What sort of system are you using, and what is the hardware
>configuration (including caches)?
Its an NEC 5074 development board with an VR5000 --
32K I and 32K D Primary cache
no secondary cache.
which vec0 code should I be using?
NEC seems to have a bunch of errata and hazards in this part when
dealing with TLBWR and friends... Is any of the existing code supposed
to respect these?
Also, arch/mips/Makefile makes the compiler use -r8000 -mips2, is
that right?
...robert
next prev parent reply other threads:[~1999-06-02 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-26 19:05 after the kernel seems to live Robert Keller
1999-05-26 20:22 ` Harald Koerfgen
1999-05-27 10:18 ` Ralf Baechle
1999-05-27 20:03 ` Robert Keller
1999-05-27 22:46 ` Ralf Baechle
1999-06-02 16:35 ` Robert Keller
1999-06-02 17:56 ` William J. Earl
1999-06-02 21:32 ` Robert Keller [this message]
1999-06-02 22:33 ` Ralf Baechle
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=4.1.19990602142531.03e112b0@poptart \
--to=rck@corp.home.net \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@uni-koblenz.de \
--cc=wje@fir.engr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.