All of lore.kernel.org
 help / color / mirror / Atom feed
From: AthlonRob <AthlonRob@axpr.net>
To: cpufreq@www.linux.org.uk
Subject: Re: [RFC] split up cpufreq.c in several files, x86 autoloader
Date: Fri, 03 Oct 2003 16:23:52 -0700	[thread overview]
Message-ID: <1065223432.13298.16.camel@dell.linux.box> (raw)
In-Reply-To: <20031003223612.GA18181@brodo.de>

On Fri, 2003-10-03 at 15:36, Dominik Brodowski wrote:

> For x86 there is a wide choice of cpufreq drivers. Especially for
> distributions and inexperienced users [no pun intended] it might become more
> and more difficult to select the best driver: "I got a mobile Pentium-4-M,
> p4-clockmod or speedstep-ich?" is one good example. Should the detection of
> the "best" cpufreq driver be made available as an optional(!)
> "cpufreq-autoload" module in arch/i386/kernel/cpu/cpufreq/?

I like that idea, as well as the module idea.

I would be sure and take in to account, however, Dell laptops not
wanting to work with some (all?) drivers in this autoload section.

Rob

      reply	other threads:[~2003-10-03 23:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03 22:36 [RFC] split up cpufreq.c in several files, x86 autoloader Dominik Brodowski
2003-10-03 23:23 ` AthlonRob [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=1065223432.13298.16.camel@dell.linux.box \
    --to=athlonrob@axpr.net \
    --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 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.