cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bas Mevissen <ml@basmevissen.nl>
To: Dominik Brodowski <linux@brodo.de>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Which cpufreq driver is best for ...
Date: Fri, 05 Sep 2003 10:15:03 +0200	[thread overview]
Message-ID: <3F584607.1060705@basmevissen.nl> (raw)
In-Reply-To: <20030904232757.GA8665@brodo.de>

Dominik Brodowski wrote:
> On Thu, Sep 04, 2003 at 02:36:45PM +0200, Bas Mevissen wrote:
> 
>>Maybe this (together with your extensive explanation in this thread) can 
>>be FAQ-ed. With a good explanation of the power saving models (clock 
>>modulation, clock modification&voltage scaling, cpu idling) a lot of 
>>questions can be answered.
> 
> Have you got some spare time? If so, a patch / file with such a FAQ /
> summary would be greatly appreciated.
> 

I don't really have much spare time, but it is a matter of priority :-)
So I'll write something in the next week. I hope people are willing to 
review it.

Regards,

Bas.

      reply	other threads:[~2003-09-05  8:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03  5:57 Which cpufreq driver is best for Norbert Preining
2003-09-03 11:37 ` Bas Mevissen
2003-09-03 14:32   ` Norbert Preining
2003-09-03 15:52     ` Mattia Dongili
2003-09-03 19:30   ` Dominik Brodowski
2003-09-03 19:50     ` Norbert Preining
2003-09-03 21:01       ` Dominik Brodowski
2003-09-04  7:09         ` Norbert Preining
2003-09-04  9:46           ` Dominik Brodowski
2003-09-04  9:59             ` Norbert Preining
2003-09-04 10:04               ` Dominik Brodowski
2003-09-04  9:57         ` Norbert Preining
2003-09-07 19:12           ` Dominik Brodowski
2003-09-04 12:25     ` Bas Mevissen
2003-09-03 19:27 ` Dominik Brodowski
2003-09-04 12:36   ` Bas Mevissen
2003-09-04 23:27     ` Dominik Brodowski
2003-09-05  8:15       ` Bas Mevissen [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=3F584607.1060705@basmevissen.nl \
    --to=ml@basmevissen.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox