| To: | "Jun Sun" <jsun@mvista.com> |
|---|---|
| Subject: | Re: CONFIG_MIPS_UNCACHED |
| From: | "Kevin D. Kissell" <kevink@mips.com> |
| Date: | Sat, 23 Jun 2001 22:15:49 +0200 |
| Cc: | <linux-mips@oss.sgi.com> |
| References: | <3B34BE3B.B72D40F1@mvista.com> <01ee01c0fc08$66e81e80$0deca8c0@Ulysses> <3B34D6AC.9EACA819@mvista.com> |
| Sender: | owner-linux-mips@oss.sgi.com |
> > Since the kernel cache attribute is never initialized before
> > ld_mmu_{whatever} is invoked, and since that Config field
> > does not have a well-defined reset state on many MIPS
> > CPUs, it would appear that we are in effect trusting the
> > bootloader to have done something reasonable like
> > set kseg0 to be non-cachable or write-through, either
> > of which would be safe for the current code.
>
> I think you just proposed a fix: check current config register when we
turn
> off cache. Thanks. :-)
That's a heuristic at best. If the config register comes up random,
it can appear to be sane even though the cache is in fact uninitialized.
Kevin K.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: CONFIG_MIPS_UNCACHED, Jun Sun |
|---|---|
| Next by Date: | [PATCH] Make sgiseeq.c 64bit ready (was: CVS Update@oss.sgi.com: linux), Thiemo Seufer |
| Previous by Thread: | Re: CONFIG_MIPS_UNCACHED, Jun Sun |
| Next by Thread: | Re: CONFIG_MIPS_UNCACHED, Jun Sun |
| Indexes: | [Date] [Thread] [Top] [All Lists] |