From: "William J. Earl" <wje@fir.engr.sgi.com>
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: SGI Linux <linux@cthulhu.engr.sgi.com>
Subject: Re: 2.1.72 precompiled with no L2
Date: Wed, 14 Jan 1998 09:48:34 -0800 [thread overview]
Message-ID: <199801141748.JAA16843@fir.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.3.95.980114120233.2369F-100000@lager.engsoc.carleton.ca>
Alex deVries writes:
>
> ftp://ftp.linux.sgi.com/pub/test/vmlinux-indy-noL2-2.1.72.tar.gz
> is available for your usage and testing.
>
> This is for machines with no L2 cache. I can't test it myself, since my
> machine does have that cache.
>
> Should L2 cache perhaps be a compiling option? Is it possible for the
> kernel to auto-detect if there's cache or not?
The L2 cache should absolutely be detected at runtime. For the R4000
and R4400, the presence of the L2 cache is in the config register
(SC bit == 0 means L2 cache is present). For the Indy R4600 and R5000
systems, an off-chip secondary cache controller is used, so you have to
probe the address of the controller to tell if it is present, or you
have to read the configuration bits from the EEPROM which contains the
memory controller and processor initialization bits as well. The EEPROM
contains both an "L2 present" bit and some bits which encode the size
of the L2 cache, which has, however, always been 512 KB. On O2, the
presence of the L2 cache, for R5000 or R10000, is encoded in the config
register. (We did not use the R5000's builtin L2 cache controller on
Indy, because the required cache RAMs were not available in time,
and the R4600 L2 cache controller could be reused without change.)
next prev parent reply other threads:[~1998-01-14 17:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-14 16:15 2.1.72 precompiled on Linus Alex deVries
1998-01-14 17:02 ` Honza Pazdziora
1998-01-14 17:02 ` Honza Pazdziora
1998-01-14 17:07 ` 2.1.72 precompiled with no L2 Alex deVries
1998-01-14 17:48 ` William J. Earl [this message]
1998-01-14 18:44 ` ralf
1998-01-14 17:13 ` 2.1.72 precompiled on Linus Honza Pazdziora
1998-01-14 17:13 ` Honza Pazdziora
1998-01-14 17:34 ` Andrew O'Brien
1998-01-15 13:44 ` Michael Hill
1998-01-15 13:44 ` Michael Hill
1998-01-15 18:32 ` Alex deVries
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=199801141748.JAA16843@fir.engr.sgi.com \
--to=wje@fir.engr.sgi.com \
--cc=adevries@engsoc.carleton.ca \
--cc=linux@cthulhu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox