From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
Brad Midgley <brad@turbolinux.com>
Cc: linuxppc-dev@lists.linuxppc.org, djosg@mgu.bath.ac.uk
Subject: Re: pmud monitoring temperature (Re: powerbook doubles)
Date: Mon, 29 Jan 2001 15:19:19 +0000 [thread overview]
Message-ID: <20010129151910.792132EF9B@apollo.valhalla.net> (raw)
> What is the maximum CPU speed for machines without clock_frequency
> present in the device tree?
wouldn't you have to go back quite a long way to find one?
My 9600 has it - and that's nearly prehistoric ;-)
Iain
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-01-29 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 15:19 Iain Sandoe [this message]
2001-01-29 16:18 ` pmud monitoring temperature (Re: powerbook doubles) Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2001-01-29 15:58 Brad Midgley
2001-01-29 1:49 Brad Midgley
2001-01-29 14:49 ` Michael Schmitz
2001-01-29 22:24 ` Troy Benjegerdes
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=20010129151910.792132EF9B@apollo.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=brad@turbolinux.com \
--cc=djosg@mgu.bath.ac.uk \
--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).