cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Graumann <johannes_graumann@web.de>
To: cpufreq@www.linux.org.uk
Subject: Crusoe and 2.6.1 confusion
Date: Fri, 23 Jan 2004 18:07:41 -0800	[thread overview]
Message-ID: <20040123180741.4e7f8452.johannes_graumann@web.de> (raw)

Hello,

I'm trying to optimize my 2.6.1 home grown kernel for my fujitsu life
book, which runs from a Transmeta Crusoe processor. I have learned from
the debian-laptop list, that this processor doesn't need any Governor or
cpufreqd, since it does the job by default.
In my .config I have the following flags set:
CPU_FREQ
X86_LONGRUN

CPU_FREQ_DEFAULT_GOV_PERFORMANCE is set as a default - even if the
Crusoe doesn't need a Governor, I can't get rid of this.

Is this all I need? Will this create the interface that longrun will
interact with?

Please help the confused!

Joh

             reply	other threads:[~2004-01-24  2:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-24  2:07 Johannes Graumann [this message]
2004-01-24 20:30 ` Crusoe and 2.6.1 confusion Dominik Brodowski

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=20040123180741.4e7f8452.johannes_graumann@web.de \
    --to=johannes_graumann@web.de \
    --cc=cpufreq@www.linux.org.uk \
    /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