From: Stefan Berndtsson <stefan@nocrew.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>
Cc: "Timothy A. Seufert" <tas@mindspring.com>,
ian geiser <geiseri@msoe.edu>,
"linuxppc-dev@lists.linuxppc.org"
<linuxppc-dev@lists.linuxppc.org>,
LinuxPPC List <linuxppc-user@lists.linuxppc.org>
Subject: Re: G3 Upgrade Questions....
Date: 29 Jul 1999 14:12:30 +0200 [thread overview]
Message-ID: <873dy77iz5.fsf@hades.nocrew.net> (raw)
In-Reply-To: Geert Uytterhoeven's message of "Thu, 29 Jul 1999 13:50:03 +0200 (CEST)"
Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be> writes:
> On 29 Jul 1999, Stefan Berndtsson wrote:
> > "Timothy A. Seufert" <tas@mindspring.com> writes:
> > > As a general rule the 750 scores about 2 bogomips per MHz, so this is
> > > suspicious too.
> >
> > On my Lombard/333 I get:
> >
> > # cat /proc/cpuinfo
> > processor : 0
> > cpu : 750
> > temperature : 0 C
> > clock : 333MHz
> > revision : 130.2
> > bogomips : 333.41
> > zero pages : total 0 (0Kb) current: 0 (0Kb) hits: 0/256 (0%)
> > machine : PowerBook1,1
> > motherboard : PowerBook1,1 MacRISC Power Macintosh
> > L2 cache : 512K unified
> > memory : 64MB
> >
> > so either it's reporting things wrong for me, or 750 doesn't always score 2/MHz.
>
> Since the 750 is derived from the 603e, it scores 1 bogomips per MHz. The 604e
> does 2 bogomips per MHz.
That's not true either.. a friends G3/300 (some stationary thing), reports 601.xx
bogomips.. unless something's screwed with _that_ setup.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-07-29 12:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87emhr7ocz.fsf@hades.nocrew.net>
1999-07-29 11:50 ` G3 Upgrade Questions Geert Uytterhoeven
1999-07-29 12:12 ` Stefan Berndtsson [this message]
1999-07-29 12:32 ` Chris Ridd
1999-07-29 12:55 ` Gabriel Paubert
1999-07-29 13:30 ` Andreas Bogk
1999-07-29 16:57 Ron Chmara
-- strict thread matches above, loose matches on Subject: below --
1999-07-29 14:11 David DeHaven
1999-07-27 22:39 ian geiser
1999-07-28 0:09 ` Paul Mackerras
1999-07-28 22:12 ` Jeremy Fitzhardinge
1999-07-29 4:46 ` Takayuki Yamaizumi
1999-07-29 9:09 ` Adrian Cox
1999-07-30 1:38 ` Takayuki Yamaizumi
1999-07-30 11:38 ` Charles Lepple
1999-07-28 4:39 ` Neil Jolly
1999-07-28 12:53 ` ian reinhart geiser (ADMIN)
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=873dy77iz5.fsf@hades.nocrew.net \
--to=stefan@nocrew.org \
--cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
--cc=geiseri@msoe.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@lists.linuxppc.org \
--cc=tas@mindspring.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.