From: Ralf Baechle <ralf@uni-koblenz.de>
To: Andrew Linfoot <andy@derfel99.freeserve.co.uk>
Cc: Ulf Carlsson <ulfc@thepuffingroup.com>,
linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr,
linux-mips@vger.rutgers.edu
Subject: Re: File corruption
Date: Mon, 28 Jun 1999 12:39:50 +0200 [thread overview]
Message-ID: <19990628123950.B735@uni-koblenz.de> (raw)
In-Reply-To: <001901bebf2d$e1951530$0a02030a@snafu>; from Andrew Linfoot on Fri, Jun 25, 1999 at 06:11:52PM +0100
On Fri, Jun 25, 1999 at 06:11:52PM +0100, Andrew Linfoot wrote:
> CPU: MIPS-R4400 FPU<MIPS-R4400FPC> ICACHE DCACHE SCACHE
This is what the firmware detected.
> Loading R4000 MMU routines.
This will always say R4000 if it's a R4000 class CPU.
> CPU revision is: 00000450
> Primary instruction cache 16kb, linesize 16 bytes)
> Primary data cache 16kb, linesize 16 bytes)
> Secondary cache sized at 1024K linesize 128
Which says that you have an R4400SC V5.0.
> an interesting point here is that /proc/cpuinfo tells me i only have an
> r4000!
Good spotting, the CPU detection code has a bug causes only V4 CPUs to be
detected as R4400. The difference is just cosmetics; R4000 and R4400 are
almost the same. Especially it's unrelated to the file corruption problem.
Ralf
next prev parent reply other threads:[~1999-06-28 21:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19990622032859.B6955@thepuffingroup.com>
[not found] ` <19990622152145.A1059@uni-koblenz.de>
1999-06-22 23:49 ` File corruption Ulf Carlsson
1999-06-24 22:28 ` Ralf Baechle
1999-06-25 13:31 ` Ulf Carlsson
1999-06-25 18:08 ` Thomas Bogendoerfer
1999-06-25 14:34 ` Andrew Linfoot
1999-06-25 14:34 ` Andrew Linfoot
1999-06-25 16:59 ` Ulf Carlsson
1999-06-25 17:11 ` Andrew Linfoot
1999-06-25 17:11 ` Andrew Linfoot
1999-06-28 10:39 ` Ralf Baechle [this message]
1999-06-28 9:34 ` Ralf Baechle
2002-09-30 19:52 File Corruption jeff leads
2002-10-01 6:10 ` Oleg Drokin
2002-10-02 4:07 ` jeff leads
2002-10-02 6:30 ` Oleg Drokin
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=19990628123950.B735@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=andy@derfel99.freeserve.co.uk \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@vger.rutgers.edu \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ulfc@thepuffingroup.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.