| To: | "Kevin D. Kissell" <KevinK@mips.com> |
|---|---|
| Subject: | Re: Strange, strange occurence |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Tue, 13 Jul 2004 02:33:17 +0200 |
| Cc: | S C <theansweriz42@hotmail.com>, linux-mips@linux-mips.org |
| In-reply-to: | <00ba01c46823$3729b200$0deca8c0@Ulysses> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <BAY2-F21njXXBARdkfw0003b0c8@hotmail.com> <20040710100412.GA23624@linux-mips.org> <00ba01c46823$3729b200$0deca8c0@Ulysses> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.1i |
On Mon, Jul 12, 2004 at 05:16:31PM +0200, Kevin D. Kissell wrote: > A truly safe and general I-cache flush routine should itself run uncached, > but a cursory glance at the linux-mips.org sources makes me think > that we do not take that precaution by default - the flush_icache_range > pointer looks to be set to the address of r4k_flush_icache_range() > function, rather than its (uncacheable) alias in kseg1. Is this something > that's fixed in a linker script, or are we just living dangerously? That's a new restriction in MIPS32 v2.0 and you're right, we're not trying to deal with it yet except for the TX49xx. Ralf |
| Previous by Date: | Re: Strange, strange occurence, Ralf Baechle |
|---|---|
| Next by Date: | Help with MOP network boot install on DECstation 5000/240, Collin Baillie |
| Previous by Thread: | Re: Strange, strange occurence, Kevin D. Kissell |
| Next by Thread: | Help with MOP network boot install on DECstation 5000/240, Collin Baillie |
| Indexes: | [Date] [Thread] [Top] [All Lists] |