From: Bruno Ducrot <ducrot@poupinou.org>
To: "Brown, Len" <len.brown@intel.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: UBUNTU - acpi battery on ACER TRAVELMATE 4000 WLMI
Date: Thu, 2 Feb 2006 00:03:22 +0100 [thread overview]
Message-ID: <20060201230322.GA11924@poupinou.org> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B3005E8FE7F@hdsmsx401.amr.corp.intel.com>
On Tue, Jan 31, 2006 at 09:35:05PM -0500, Brown, Len wrote:
>
> >On Fri, Jan 27, 2006 at 02:05:23PM -0500, Brown, Len wrote:
> >> Also, you may find that the current speedstep-centrino
> >> is able to load on this system. Without hard-coded tables
> >> for this processor family/model/stepping, it too would use
> >> the ACPI PSS, but it would use native MSR access, which
> >> is lower overhead than the IO port access used by acpi-cpufreq.
> >> (in the future, acpi-cpufreq and speedstep-centrino should
> >> be combined into a single driver)
> >
> >Do you mean you want to combine all possible drivers into only
> >one? That is at that time of writing:
> >
> >acpi-cpufreq (IO version), speedstep-centrino, powernow-k7
> >and powernow-k8?
> >
> >Well, it might be possible that some cpufreq devellopers
> >would be against this approach I'm afraid.
>
> acpi-cpufreq + speedstep-centrino = intel-enhanced-speedstep
I see. I thought you wanted to kill processor_perflib.c. I was
indeed wrong. I would like to point that acpi-cpufreq could also be
somewhat in "conflict" with speedstep-smi and speedstep-ich.
That remind me that acpi-cpufreq is not only intel enhanced speedstep (a
la Pentium Mobile, or Xeons, I means), but can work on some Pentium III
or IV IIRC.
> unless you can think of a better name. Both acpi-cpufreq
> and speedstep-centrino turn out not to be good names,
> since they don't describe either the function of the driver
> or what hardware they run on.
Especially for speedstep-centrino. I'm not sure for acpi-cpufreq
though, but it's true this driver works only with Intel processors.
> No, it wouldn't' make sense to combine the intel and amd drivers.
Well, a BIOS writer could write a SMI handler (after all,
they have the right to do what they want) in order to support
acpi-cpufreq for an AMD processor, but I highly doubt this will
ever happens. It's simply too late now.
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2006-02-01 23:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 2:35 UBUNTU - acpi battery on ACER TRAVELMATE 4000 WLMI Brown, Len
2006-02-01 23:03 ` Bruno Ducrot [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-01 2:36 Brown, Len
2006-02-01 10:53 ` Johan Vromans
2006-01-27 19:05 Brown, Len
2006-01-28 15:20 ` Johan Vromans
2006-01-30 11:25 ` Bruno Ducrot
2006-01-26 20:27 Brown, Len
2006-01-27 11:43 ` Johan Vromans
[not found] <821d061d0601261146j1101d50ew@mail.gmail.com>
2006-01-26 19:52 ` Marco Giumelli
2006-01-27 6:38 ` martin
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=20060201230322.GA11924@poupinou.org \
--to=ducrot@poupinou.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.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 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.