From: Ron Chmara <ron@Opus1.COM>
To: linuxppc-dev@lists.linuxppc.org, linuxppc-user@lists.linuxppc.org
Subject: Re: G3 Upgrade Questions....
Date: Thu, 29 Jul 1999 09:57:01 -0700 [thread overview]
Message-ID: <37A087DD.D896B257@opus1.com> (raw)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
On Thu, 29 Jul 1999, Chris Ridd wrote:
> On 29 Jul 1999 14:12:30 +0200, Stefan Berndtsson wrote:
> > That's not true either.. a friends G3/300 (some stationary thing), reports $> > bogomips.. unless something's screwed with _that_ setup.
> Well they *are* *BOGO*mips after all ;-)
http://linux.com/howto/mini/BogoMips.html#toc1
http://linux.com/howto/mini/BogoMips-2.html
http://linux.com/howto/mini/BogoMips-9.html
There aren't many entries for the 750 series (okay, there's one), so
maybe
we need to send some info off to baron@clifton.hobby.nl, so he can
update
the howto's.
-Bop
[[ 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 reply other threads:[~1999-07-29 16:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-29 16:57 Ron Chmara [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-07-29 14:11 G3 Upgrade Questions David DeHaven
[not found] <87emhr7ocz.fsf@hades.nocrew.net>
1999-07-29 11:50 ` Geert Uytterhoeven
1999-07-29 12:12 ` Stefan Berndtsson
1999-07-29 12:32 ` Chris Ridd
1999-07-29 12:55 ` Gabriel Paubert
1999-07-29 13:30 ` Andreas Bogk
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=37A087DD.D896B257@opus1.com \
--to=ron@opus1.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@lists.linuxppc.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).