All of lore.kernel.org
 help / color / mirror / Atom feed
From: shane@bogomip.com
To: Dominik Brodowski <linux@brodo.de>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Transmeta Longrun Support?
Date: Mon, 23 Jun 2003 10:51:10 -0600	[thread overview]
Message-ID: <20030623165110.GD5108@bogomip.com> (raw)
In-Reply-To: <20030623134842.GE2330@brodo.de>

On Mon, Jun 23, 2003 at 03:48:42PM +0200, Dominik Brodowski wrote:
> On Sun, Jun 22, 2003 at 01:44:39PM -0600, shane@bogomip.com wrote:
> > What does the cpufreq driver offer crusoe kernels that the longrun userspace utility can't already do.
> > 
> > Just a standard proc interface to the settings?

> AFAIK, yes. I'm not aware of that userspace utility, though. 
> 	Dominik

http://freshmeat.net/projects/longrun/

I initially started using this, when I wasn't aware of the CPUFreq project.

So CPUFreq doesn't modify the vm or do proc monitoring in the kernel to come up 
with better times to turn on fans and the like?

Shane

      parent reply	other threads:[~2003-06-23 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-22 19:44 Transmeta Longrun Support? shane
     [not found] ` <20030623134842.GE2330@brodo.de>
2003-06-23 16:51   ` shane [this message]

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=20030623165110.GD5108@bogomip.com \
    --to=shane@bogomip.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=linux@brodo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.