From: Tom Rini <trini@kernel.crashing.org>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: Albrecht Dreß <ad@mpifr-bonn.mpg.de>, linuxppc-dev@lists.linuxppc.org
Subject: Re: CPU Temperature Patch
Date: Wed, 20 Sep 2000 19:24:32 -0700 [thread overview]
Message-ID: <20000920192432.T472@opus.bloom.county> (raw)
In-Reply-To: <Pine.LNX.4.10.10009202113230.7561-100000@opal.biophys.uni-duesseldorf.de>; from schmitz@opal.biophys.uni-duesseldorf.de on Wed, Sep 20, 2000 at 09:15:27PM +0200
On Wed, Sep 20, 2000 at 09:15:27PM +0200, Michael Schmitz wrote:
> > > > + /* this set for 500 MHz Pismo - how do we get access to clock?? */
> > >
> > > There is, in the same file, around line 319 code to read the clock speed from
> > > the device tree. However, is it really necessary to include the clock speed at
> > > this point? What is the drawback if we just assume 500 MHz (or even the max
> > > value) for every G3 based machine?
> >
> > Why assume when we can do it properly? Besides, a friend of mine oc'ed his
> > B&W to 550, so it's possible to have >500Mhz :)
>
> Like this?
Looks almost sane.
> @@ -208,9 +209,23 @@
> /* we need 20us to do the compare - assume 300MHz processor clock */
> /* max value for sitv is 0x3fff - or 16383 */
> /* this set for 500 MHz Pismo - how do we get access to clock?? */
> +
> + cpu_freq = 500;
But why 500 here? The bit for reading temp is on all G3s, yes? And since
we assume 300Mhz clock, which is the middle of the clock ranges (close enough)
shouldn't this be 300 as well?
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-21 2:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11420.10009201242@mgu.bath.ac.uk>
2000-09-20 12:42 ` CPU Temperature Patch D.J. Osguthorpe
2000-09-20 15:03 ` Albrecht Dre_
2000-09-20 18:04 ` Tom Rini
2000-09-20 19:15 ` Michael Schmitz
2000-09-21 2:24 ` Tom Rini [this message]
2000-09-21 19:40 ` Michel Lanners
2000-09-21 19:02 ` Michel Lanners
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=20000920192432.T472@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=ad@mpifr-bonn.mpg.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.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 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).