All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark Chambers" <mwchambers@citlink.net>
To: "Wolfgang Denk" <wd@denx.de>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Motorola 5200 MIPS
Date: Mon, 3 May 2004 13:33:06 -0400	[thread overview]
Message-ID: <005d01c43134$b2c19cf0$0301a8c0@chuck2> (raw)
In-Reply-To: 20040503153304.34906C109F@atlas.denx.de


> Then go back and read the archives. This has been  discussed  several
> times before.
>

An excellent idea.  Why didn't I think of that?  And to all of you fellow
nerds back there who also like to know how things work and why - bless your
heart.  Actually, I don't fully follow the explanations, but clearly the 603
core is not able to execute a single looped dbnz once per clock, so 263
BogoMIPS is a reasonable number for a 396MHz 5200.  The number does not have
anything to do with bus speed, which is part of what was bothering me (2 x
132MHz, you know).  I won't pester you all with this any more but if anybody
else wants to discuss further I'd welcome your emails  (not discuss BogoMIPS
necessarily, but details of 5200 performance - I've got some very
challenging requirements to hit and any insights will be welcome).

Mark Chambers


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2004-05-03 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-30 22:25 Motorola 5200 MIPS Mark Chambers
2004-04-30 22:46 ` Gary Thomas
2004-05-03  6:56 ` Gerrit Van de Velde
2004-05-03 14:39   ` Mark Chambers
2004-05-03 15:32     ` Wolfgang Denk
2004-05-03 17:33       ` Mark Chambers [this message]

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='005d01c43134$b2c19cf0$0301a8c0@chuck2' \
    --to=mwchambers@citlink.net \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=wd@denx.de \
    /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.