From: Troy Benjegerdes <hozer@drgw•net>
To: Michael Schmitz <schmitz@opal•biophys.uni-duesseldorf.de>
Cc: Brad Midgley <brad@turbolinux•com>,
linuxppc-dev@lists•linuxppc.org, djosg@mgu•bath.ac.uk
Subject: Re: pmud monitoring temperature (Re: powerbook doubles)
Date: Mon, 29 Jan 2001 16:24:25 -0600 [thread overview]
Message-ID: <20010129162425.A21300@altus.drgw.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0101291534510.2636-200000@opal.biophys.uni-duesseldorf.de>; from schmitz@opal.biophys.uni-duesseldorf.de on Mon, Jan 29, 2001 at 03:49:02PM +0100
On Mon, Jan 29, 2001 at 03:49:02PM +0100, Michael Schmitz wrote:
> > i reworked this patch to work with the current bk tree (argh. i just complained to iain that diffs
> > against a moving target were gross)
> >
> > http://redcloud.uccs.edu/~bcmidgle/linux/
> >
> > btw, it looks like troy wants the _{gs}et_THRM{123} macros changed to use some different macros,
> > but i'm not familiar with that stuff so i just reenabled the old macros.
>
> I don't think what changes you propose there but from the comment on your
> patch page ('cpu speed not included in calculations') it seems you picked
> up the old version of the patch. I attach the version including
> conversion time calculation from processor speed (for 2.4.0pre). The CPU
> speed is preset to 500 MHz in case it can't be determined from OF, this
> gives too long conversion times for slower processors - does this hurt?
> What is the maximum CPU speed for machines without clock_frequency
> present in the device tree?
Guys, you should *really* take a look at the CONFIG_TAU stuff in linuxppc_2_5.
It's interrupt driven, so the delay doesn't really matter, and you can't cause
a DOS by infinitely re-reading /proc/cpuinfo.
And does anyone think this is tested enough to move to linuxppc_2_4?
--------------------------------------------------------------------------
Troy Benjegerdes 'da hozer' hozer@drgw•net
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-29 22:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 1:49 pmud monitoring temperature (Re: powerbook doubles) Brad Midgley
2001-01-29 14:49 ` Michael Schmitz
2001-01-29 22:24 ` Troy Benjegerdes [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-29 15:58 Brad Midgley
2001-01-29 15:19 Iain Sandoe
2001-01-29 16:18 ` Benjamin Herrenschmidt
2001-01-28 20:25 Brad Midgley
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=20010129162425.A21300@altus.drgw.net \
--to=hozer@drgw$(echo .)net \
--cc=brad@turbolinux$(echo .)com \
--cc=djosg@mgu$(echo .)bath.ac.uk \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=schmitz@opal$(echo .)biophys.uni-duesseldorf.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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