Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jsun@mvista.com (Jun Sun), carlson@sibyte.com, linux-mips@oss.sgi.com
Subject: Re: broken RM7000 in CVS ...
Date: Mon, 15 Jan 2001 06:37:25 -0200	[thread overview]
Message-ID: <20010115063725.C8866@bacchus.dhis.org> (raw)
In-Reply-To: <E14HDwC-0005GH-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Jan 12, 2001 at 11:48:50PM +0000

On Fri, Jan 12, 2001 at 11:48:50PM +0000, Alan Cox wrote:

> > My understanding is that we don't have a standard way to probe for external
> > cache (L2 or L3).  So this problem is not only for MIPS32 cpus.
> 
> Cache is very arch specific. You don't want to know how you find L2 cache
> on a MacII for example 8)

Actually the Indy's R4600 / R5000 second level caches also call for the use
of LARTs in a while (1) loop ;-)  Read the generic code had to be changed
in order to support in a sane way.

  Ralf

WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@oss.sgi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jun Sun <jsun@mvista.com>, carlson@sibyte.com, linux-mips@oss.sgi.com
Subject: Re: broken RM7000 in CVS ...
Date: Mon, 15 Jan 2001 06:37:25 -0200	[thread overview]
Message-ID: <20010115063725.C8866@bacchus.dhis.org> (raw)
Message-ID: <20010115083725.Dlqq5J4_YgDw8ph9YApuz6MGkBtOr7iqnfJ6HECTaow@z> (raw)
In-Reply-To: <E14HDwC-0005GH-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Jan 12, 2001 at 11:48:50PM +0000

On Fri, Jan 12, 2001 at 11:48:50PM +0000, Alan Cox wrote:

> > My understanding is that we don't have a standard way to probe for external
> > cache (L2 or L3).  So this problem is not only for MIPS32 cpus.
> 
> Cache is very arch specific. You don't want to know how you find L2 cache
> on a MacII for example 8)

Actually the Indy's R4600 / R5000 second level caches also call for the use
of LARTs in a while (1) loop ;-)  Read the generic code had to be changed
in order to support in a sane way.

  Ralf

  parent reply	other threads:[~2001-01-15  8:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-12  3:54 broken RM7000 in CVS Jun Sun
2001-01-12  7:23 ` Kevin D. Kissell
2001-01-12  7:23   ` Kevin D. Kissell
2001-01-12 18:58   ` Jun Sun
2001-01-12 19:06     ` Justin Carlson
2001-01-12 20:27       ` Jun Sun
2001-01-12 20:29         ` Justin Carlson
2001-01-12 21:39           ` Jun Sun
2001-01-12 23:48         ` Alan Cox
2001-01-12 23:48           ` Alan Cox
2001-01-15  8:37           ` Ralf Baechle [this message]
2001-01-15  8:37             ` Ralf Baechle
2001-01-12 19:42     ` Kevin D. Kissell
2001-01-12 19:42       ` Kevin D. Kissell
2001-01-15  8:42       ` Ralf Baechle
2001-01-15  8:42         ` 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=20010115063725.C8866@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=carlson@sibyte.com \
    --cc=jsun@mvista.com \
    --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