From: Ralf Baechle <ralf@linux-mips.org>
To: "Kevin D. Kissell" <KevinK@mips.com>
Cc: S C <theansweriz42@hotmail.com>, linux-mips@linux-mips.org
Subject: Re: Strange, strange occurence
Date: Tue, 13 Jul 2004 02:33:17 +0200 [thread overview]
Message-ID: <20040713003317.GA26715@linux-mips.org> (raw)
In-Reply-To: <00ba01c46823$3729b200$0deca8c0@Ulysses>
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
next prev parent reply other threads:[~2004-07-13 0:33 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 18:50 Strange, strange occurence S C
2004-07-10 7:33 ` Niels Sterrenburg
2004-07-10 10:04 ` Ralf Baechle
2004-07-12 15:16 ` Kevin D. Kissell
2004-07-12 15:16 ` Kevin D. Kissell
2004-07-13 0:33 ` Ralf Baechle [this message]
2004-07-13 7:49 ` Help with MOP network boot install on DECstation 5000/240 Collin Baillie
2004-07-13 8:03 ` Jan-Benedict Glaw
2004-07-14 6:57 ` Collin Baillie
2004-07-14 9:54 ` Maciej W. Rozycki
2004-07-14 12:44 ` Jan-Benedict Glaw
2004-07-14 12:51 ` Maciej W. Rozycki
2004-07-14 13:30 ` Jan-Benedict Glaw
2004-07-15 11:33 ` Maciej W. Rozycki
2004-07-14 12:43 ` Jan-Benedict Glaw
2004-07-16 14:41 ` Collin Baillie
2004-07-16 15:04 ` Jan-Benedict Glaw
2004-07-16 15:13 ` Maciej W. Rozycki
2004-07-16 15:08 ` Maciej W. Rozycki
2004-07-16 16:31 ` Thiemo Seufer
2004-07-16 16:51 ` Maciej W. Rozycki
2004-07-16 18:56 ` Thiemo Seufer
2004-07-13 15:31 ` Strange, strange occurence Kevin D. Kissell
2004-07-13 15:31 ` Kevin D. Kissell
2004-07-14 12:02 ` Maciej W. Rozycki
2004-07-14 16:35 ` Dominic Sweetman
2004-07-14 17:45 ` Michael Uhler
2004-07-14 17:45 ` Michael Uhler
2004-07-15 1:34 ` Atsushi Nemoto
2004-07-15 1:53 ` Ralf Baechle
2004-07-16 12:24 ` Ralf Baechle
2004-07-16 16:05 ` Atsushi Nemoto
-- strict thread matches above, loose matches on Subject: below --
2004-07-12 20:49 S C
2004-07-12 21:23 S C
2004-07-12 21:48 ` Kevin D. Kissell
2004-07-12 21:48 ` Kevin D. Kissell
2004-07-12 22:25 ` Kevin D. Kissell
2004-07-12 22:25 ` Kevin D. Kissell
2004-07-12 23:13 ` Ralf Baechle
2004-07-12 23:11 ` Ralf Baechle
2004-07-12 23:00 ` Ralf Baechle
2004-07-12 23:10 S C
2004-07-30 21:06 G H
2004-07-31 5:09 ` 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=20040713003317.GA26715@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=KevinK@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=theansweriz42@hotmail.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.