linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <brad@turbolinux.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: powerbook doubles as a frying pan
Date: Mon, 29 Jan 2001 12:01:26 +0100	[thread overview]
Message-ID: <19341224043310.26390@mailhost.mipsys.com> (raw)
In-Reply-To: <200101280019.QAA15270@mail.turbolinux.com>


>
>is everyone *totally* sure that activating the fan is entirely handled in
>hardware? is there no
>register for controlling the threshold?

I've seen nothing in Apple's own Darwin OS related to controlling the
powerbook fan neither. However, they do have code that use the CPU's
temperature sensors to control the ICTC (instruction cache throttling).

Troy have some code that allow to read the temp from /proc. However, it
looks like a lot of CPUs are so badly calibrated that the information
returned is almost useless... Maybe that's not the case in CPUs used in
portables, that's the case in some of the G4s used in dual G4s.

>/proc/cpuinfo does not report the temperature (i'm not sure the hardware
>can report it).
>
>for now, i put it to sleep whenever it gets hot. i suppose i should put
>sleep statements in
>anything that is cpu bound to save the machine. also i pull out the pc
>card if it's not in use to
>help with ventilation.
>
>(what a day i'm having... i just got it back and spent the day trying to
>find out why java would
>not run. after examing working- and non-working-strace's i noticed that
>the date was set to 1904.
>the java vm will not initialize with a date like that. maybe it's because
>sun realizes that no
>java machine was known to be working in the year 1904.)


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-01-29 11:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-28  0:27 powerbook doubles as a frying pan Brad Midgley
2001-01-29 11:01 ` Benjamin Herrenschmidt [this message]
2001-01-29 15:15   ` Michael Schmitz
2001-01-29 15:30     ` Chas Williams
2001-01-29 21:54   ` Troy Benjegerdes
2001-02-03  3:15     ` Dan Bethe
2001-01-31  5:36   ` Timothy A. Seufert
2001-02-03  3:03     ` Dan Bethe
2001-02-03 23:24       ` Timothy A. Seufert
2001-02-05 12:46       ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2001-01-28  1:09 Iain Sandoe
2001-01-29 15:27 Iain Sandoe

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=19341224043310.26390@mailhost.mipsys.com \
    --to=benh@kernel.crashing.org \
    --cc=brad@turbolinux.com \
    --cc=linuxppc-dev@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).