Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Rojhalat Ibrahim <ibrahim@schenk.isar.de>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: More than 512MB of memory
Date: Mon, 07 Feb 2005 09:10:12 +0100	[thread overview]
Message-ID: <42072264.6000001@schenk.isar.de> (raw)
In-Reply-To: <20050204004028.GC22311@linux-mips.org>

Ralf Baechle wrote:
> On Tue, Jan 18, 2005 at 03:44:51PM +0100, Rojhalat Ibrahim wrote:
> 
> 
>>is there anything special I have to do
>>when I want to use more than 512MB of memory?
>>My Yosemite board works fine with 512MB
>>but when I try 1GB it crashes in 32bit mode
>>with highmem and also in 64bit mode.
>>The boot monitor (PMON) maps the 1024MB
>>to physical addresses 0x0000.0000 - 0x4000.0000.
> 
> 
> Can you try below patch?
> 
>   Ralf
> 
> --- linux/arch/mips/mm/c-r4k.c	2004-12-07 02:30:50.000000000 +0000
> +++ linux/arch/mips/mm/c-r4k.c	2005-02-04 00:31:34.623814760 +0000
> @@ -566,7 +566,10 @@
>  
>  	if (!cpu_has_ic_fills_f_dc) {
>  		unsigned long addr = (unsigned long) page_address(page);
> -		r4k_blast_dcache_page(addr);
> +		if (addr)
> +			r4k_blast_dcache_page(addr);
> +		else
> +			r4k_blast_dcache();
>  		if (!cpu_icache_snoops_remote_store)
>  			r4k_blast_scache_page(addr);
>  		ClearPageDcacheDirty(page);
> 


With a slightly extended patch it actually works. But afterwards
I get a lot of Illegal instructions and Segmentation faults, where
there shouldn't be any. Below is the patch I used.

Thanks
Rojhalat Ibrahim


--- linux/arch/mips/mm/c-r4k.c  2005-01-03 10:23:27.000000000 +0100
+++ linux-2.6.10/arch/mips/mm/c-r4k.c   2005-02-07 09:04:27.000000000 +0100
@@ -566,9 +566,17 @@

         if (!cpu_has_ic_fills_f_dc) {
                 unsigned long addr = (unsigned long) page_address(page);
-               r4k_blast_dcache_page(addr);
+               if (addr)
+                       r4k_blast_dcache_page(addr);
+               else
+                       r4k_blast_dcache();
                 if (!cpu_icache_snoops_remote_store)
-                       r4k_blast_scache_page(addr);
+               {
+                       if (addr)
+                               r4k_blast_scache_page(addr);
+                       else
+                               r4k_blast_scache();
+               }
                 ClearPageDcacheDirty(page);
         }

  reply	other threads:[~2005-02-07  8:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-18 14:44 More than 512MB of memory Rojhalat Ibrahim
2005-01-18 15:49 ` Manish Lachwani
2005-01-18 17:13   ` Rojhalat Ibrahim
2005-02-03 15:35 ` Ralf Baechle
2005-02-03 18:20   ` Manish Lachwani
2005-02-04  0:01     ` Ralf Baechle
2005-02-04  0:40 ` Ralf Baechle
2005-02-07  8:10   ` Rojhalat Ibrahim [this message]
2005-02-08  0:17     ` Ralf Baechle
2005-02-08  9:57       ` Rojhalat Ibrahim
2005-02-09  0:06         ` Ralf Baechle
2005-02-09  8:06           ` Rojhalat Ibrahim
2005-02-10 13:40             ` Ralf Baechle
2005-02-10 14:54               ` Rojhalat Ibrahim
2005-02-10 15:10               ` Rojhalat Ibrahim
2005-02-09 15:41         ` Rojhalat Ibrahim
2005-02-09 18:14           ` 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=42072264.6000001@schenk.isar.de \
    --to=ibrahim@schenk.isar.de \
    --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