Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Chris Dearman <chris@mips.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: [PATCH] waybit not set for MIPS32/MIPS64 caches
Date: Tue, 15 Apr 2003 14:01:28 +0100	[thread overview]
Message-ID: <3E9C02A8.4090008@mips.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 336 bytes --]

Hi Ralf,
   The unified cache code (c-r4k.c) does not set the waybit for 
MIPS32/MIPS64 processors.  This patch needs to be applied to 
{mips,mips64}/mm/c-r4k.c in 2.4 and 2.5.

	Chris

-- 
Chris Dearman          The Fruit Farm, Ely Road    voice +44 1223 706206
MIPS Technologies (UK) Chittering, Cambs, CB5 9PH  fax   +44 1223 706250

[-- Attachment #2: cache.diffs --]
[-- Type: text/plain, Size: 750 bytes --]

Index: arch/mips/mm/c-r4k.c
===================================================================
RCS file: /home/cvs/linux/arch/mips/mm/c-r4k.c,v
retrieving revision 1.3.2.40
diff -u -r1.3.2.40 c-r4k.c
--- arch/mips/mm/c-r4k.c	14 Apr 2003 03:49:59 -0000	1.3.2.40
+++ arch/mips/mm/c-r4k.c	15 Apr 2003 12:47:58 -0000
@@ -738,6 +738,7 @@
 		icache_size = c->icache.sets *
 		              c->icache.ways *
 		              c->icache.linesz;
+		c->icache.waybit = ffs(icache_size/c->icache.ways) - 1;
 
 		/*
 		 * Now probe the MIPS32 / MIPS64 data cache.
@@ -754,6 +755,7 @@
 		dcache_size = c->dcache.sets *
 		              c->dcache.ways *
 		              c->dcache.linesz;
+		c->dcache.waybit = ffs(dcache_size/c->dcache.ways) - 1;
 		break;
 	}
 

             reply	other threads:[~2003-04-15 13:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 13:01 Chris Dearman [this message]
2003-04-15 15:01 ` [PATCH] waybit not set for MIPS32/MIPS64 caches 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=3E9C02A8.4090008@mips.com \
    --to=chris@mips.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    /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