From: art <art@sigrand.ru>
To: linux-mips@linux-mips.org
Cc: macro@linux-mips.org, ralf@linux-mips.org, rongkai.zhan@windriver.com
Subject: Re: Problem with TLB mcheck!
Date: Wed, 31 May 2006 18:02:34 +0700 [thread overview]
Message-ID: <8751.060531@sigrand.ru> (raw)
Hello , All
I think I'm on wright way:
I change /arch/mips/mm/tlbex.c:
--- /home/artpol/router/buildroot/kernels/linux-2.6.16-old/arch/mips/mm/tlbex.c 2006-03-20 11:35:39.000000000 +0000
+++ tlbex.c 2006-05-31 16:57:58.000000000 +0000
@@ -742,7 +742,7 @@
}
#endif
- memcpy((void *)CAC_BASE, tlb_handler, 0x80);
+ memcpy((void *)ebase, tlb_handler, 0x80);
}
/*
@@ -838,6 +838,7 @@
break;
case CPU_R4300:
+ case CPU_4KC:
case CPU_5KC:
case CPU_TX49XX:
case CPU_AU1000:
@@ -852,13 +853,12 @@
case CPU_R10000:
case CPU_R12000:
- case CPU_4KC:
case CPU_SB1:
case CPU_SB1A:
case CPU_4KSC:
case CPU_20KC:
case CPU_25KF:
- tlbw(p);
+ tlbw(p);
break;
case CPU_NEVADA:
@@ -1260,7 +1260,7 @@
}
#endif
- memcpy((void *)CAC_BASE, final_handler, 0x100);
+ memcpy((void *)ebase, final_handler, 0x100);
}
And it seem than no problem now (`cat /bin/busybox > box` work as much
as need!).
I think this is wright way, but not all - I'am not guru in memory
subsystem and can miss something! So wait for your advices!
--
Best regards,
art mailto:art@sigrand.ru
next reply other threads:[~2006-05-31 11:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 11:02 art [this message]
2006-05-31 11:27 ` Problem with TLB mcheck! Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2006-05-31 4:18 Zhan, Rongkai
2006-05-31 4:18 ` Zhan, Rongkai
2006-05-31 3:42 art
2006-05-24 9:35 art
2006-05-24 12:45 ` Maciej W. Rozycki
2006-05-24 14:49 ` Ralf Baechle
2006-05-24 15:11 ` Maciej W. Rozycki
2006-05-24 15:52 ` Ralf Baechle
2006-05-24 16:29 ` Maciej W. Rozycki
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=8751.060531@sigrand.ru \
--to=art@sigrand.ru \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=rongkai.zhan@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.