Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@uni-koblenz.de>
To: Robert Keller <rck@corp.home.net>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: after the kernel seems to live
Date: Fri, 28 May 1999 00:46:32 +0200	[thread overview]
Message-ID: <19990528004632.B608@uni-koblenz.de> (raw)
In-Reply-To: <4.1.19990527124423.00930cd0@mail>; from Robert Keller on Thu, May 27, 1999 at 01:03:32PM -0700

On Thu, May 27, 1999 at 01:03:32PM -0700, Robert Keller wrote:

> At 12:18 PM 5/27/99 +0200, Ralf Baechle wrote:
> >What CPU is being used on that eval board?  If it's one that isn't yet
> >supported in our sources then I suspect you have a problem either with the
> >cacheflushing routines themselfes or the calls to them in the network
> >driver.  What NIC are you using, btw?  We've got patches around for a
> >couple of those which are most often being used with MIPS machines.
> 
> Its a VR5000 (D30500S2),  2.2.1 seems to recognize it as a
> type 24 (0x18).  Presently, I'm using a PCI 3c905 despite the
> fact that the eval board has a 21140 (albeit with a completely
> bogus SROM) built in to it.  I have my own patches to 3c59x.c
> tulip.c and even tlan.c to get them working to varying degrees.
> I'd still be interested in comparing my patches with the ones
> you have...

The R5000 is supported and known to work.  You happen to have a
second level cache on that board?

> How can I make sure that I'm not haveing cacheflushing problems?

Debugging :-)

In particular the ring structures are nasty, allocate them as uncached
memory in KSEG1.  In general the rule is that you should try to handle
as much in uncached memory as possible when debugging such problems.
That's of course very bad for performance but it helps.

> I'm presently using declinuxroot-990518.tgz from ftp.linux.sgi.com,
> so should I assume that it should just work?

Yes, it should.

  Ralf

  reply	other threads:[~1999-05-27 22:49 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 [this message]
1999-06-02 16:35       ` Robert Keller
1999-06-02 17:56         ` William J. Earl
1999-06-02 21:32           ` Robert Keller
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=19990528004632.B608@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=rck@corp.home.net \
    /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