Date: Wed, 17 May 2006 12:17:49 +0900
Message-ID: <87ves59w6a.dancerj%dancer@netfort.gr.jp>
From: Junichi Uekawa <dancer@netfort.gr.jp>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Junichi Uekawa <dancer@netfort.gr.jp>, linux-kernel@vger.kernel.org,
       debian-powerpc@lists.debian.org
Subject: Re: ppc: bogomips at 73 when CPU is at 1GHz
In-Reply-To: <1147819034.6753.17.camel@localhost.localdomain>
References: <87ac9hzn1g.dancerj%dancer@netfort.gr.jp>
	<1147819034.6753.17.camel@localhost.localdomain>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8
 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/21.4 (powerpc-unknown-linux-gnu)
 MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 998
Lines: 32

Hi,

> > I've noticed the very log value on bogomips on self-compiled 2.6.16.16
> > on iBook G4.
> 
>  .../...
> 
> Normal. We don't use CPU bogo loops for short timings, we use the CPU
> timebase instead, thus you now get bogomips derived from the timebae
> frequency of the machine.

Thanks.

I was tracking down a possibly unrelated problem with USB wlan device
(GW-US11H) and suspected this to be a cause of the problem.


Incidentally, if anyone has any success using USB wlan device
(GW-US11H), I'd like to hear that ... it's rather inconvenient to be
at Debian Conference with a wireless connection that hangs your
machine after 5 minutes.

http://www.netfort.gr.jp/~dancer/diary/daily/2006-May-17.html.en#2006-May-17-05:18:32


regards,
	junichi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/