From: Bruno Ducrot <ducrot@poupinou.org>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH 3/8] acpi-cpufreq: merge acpi functionality of cpufreq drivers
Date: Mon, 7 Aug 2006 10:48:49 +0200 [thread overview]
Message-ID: <20060807084849.GP17014@poupinou.org> (raw)
In-Reply-To: <20060804170338.GK7265@redhat.com>
On Fri, Aug 04, 2006 at 01:03:38PM -0400, Dave Jones wrote:
> On Fri, Aug 04, 2006 at 11:22:12AM +0200, Bruno Ducrot wrote:
>
> > > Newer VIA CPUs rely on this driver rather than longhaul for example.
> >
> > Ah I see. In fact we could add them already to
> > speedstep-centrino.c easily.
>
> We could, though they need to rely on the ACPI tables rather than
> hardcoded tables (as we've no way to distinguish regular from ULV
> parts afaics), at which point it doesn't really buy us anything
> over just using acpi-cpufreq which works without any modifications.
I don't get it. speedstep-centrino does support both hardcoded tables
and ACPI tables (but I agree it would be better to add this support
to acpi-cpufreq instead of speedstep-centrino).
FYI FreeBSD support VIA C7-M processors with hardcoded tables. They
use MSR_IA32_PERF_STATUS, bit 31 to 64, in order to distinguish various
variants of those processors (and Intel processors as well btw).
See /sys/i386/cpufreq/est.c
http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/i386/cpufreq/est.c?rev=1.11&content-type=text/plain
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2006-08-07 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 18:44 [PATCH 3/8] acpi-cpufreq: merge acpi functionality of cpufreq drivers Alexey Starikovskiy
2006-08-02 9:27 ` Bruno Ducrot
2006-08-02 18:44 ` Alexey Starikovskiy
2006-08-03 16:11 ` Bruno Ducrot
2006-08-03 16:20 ` Dave Jones
2006-08-03 17:05 ` Alexey Starikovskiy
2006-08-04 9:22 ` Bruno Ducrot
2006-08-04 17:03 ` Dave Jones
2006-08-07 8:48 ` Bruno Ducrot [this message]
2006-08-07 16:55 ` Dave Jones
2006-08-03 16:28 ` Alexey Starikovskiy
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=20060807084849.GP17014@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
/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.