| To: | ralf@uni-koblenz.de |
|---|---|
| Subject: | Re: Indy crash during bootup |
| From: | "William J. Earl" <wje@fir.engr.sgi.com> |
| Date: | Thu, 11 Dec 1997 19:15:22 -0800 |
| Cc: | linux@cthulhu.engr.sgi.com |
| In-reply-to: | <19971212033448.01867@uni-koblenz.de> |
| References: | <19971208150602.52582@brian.uni-koblenz.de> <ralf@uni-koblenz.de> <9712091934.ZM3116@mdhill.interlog.com> <19971210040210.27443@uni-koblenz.de> <9712110612.ZM1219@mdhill.interlog.com> <19971212033448.01867@uni-koblenz.de> |
| Sender: | owner-linux@cthulhu.engr.sgi.com |
ralf@uni-koblenz.de writes:
...
> William: would an attempt to manipulate the R4600 second level cache on
> a Indy without such a cache result in a bus error interrupt?
...
Yes. The memory address of the cache controller will not exist. Avoid
referencing it when the cache is not configured. If the kernel is not
reading the cache configuration from the CPU module EEPROM, then it should
test for the existence of the cache controller by referencing it within
some sort of exception trap which returns control gracefully with an error
indication if a bus error occurs. Note that you might get a bus error exception
(on a read) rather than a bus error interrupt (on a write).
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Uploads ..., ralf |
|---|---|
| Next by Date: | Re: Indy crash during bootup, ralf |
| Previous by Thread: | Indy crash during bootup, ralf |
| Next by Thread: | Re: Indy crash during bootup, ralf |
| Indexes: | [Date] [Thread] [Top] [All Lists] |