From: Bruno Ducrot <ducrot@poupinou.org>
To: Alexey Starikovskiy <alexey_y_starikovskiy@linux.intel.com>
Cc: cpufreq@lists.linux.org.uk, Dave Jones <davej@redhat.com>
Subject: Re: [PATCH 3/8] acpi-cpufreq: merge acpi functionality of cpufreq drivers
Date: Thu, 3 Aug 2006 18:11:30 +0200 [thread overview]
Message-ID: <20060803161130.GL17014@poupinou.org> (raw)
In-Reply-To: <44D0F292.8090403@linux.intel.com>
On Wed, Aug 02, 2006 at 10:44:34PM +0400, Alexey Starikovskiy wrote:
> Bruno Ducrot wrote:
> > I've not checked carrefully but it seems to me you are breaking
> > powernow-k8.
> We do not touch powernow-k8, and tried to make sure we do not change
> acpi-cpufreq to exclude any unknown hardware. What we tried to do, is to merge
> different ways of accessing cpufreq with ACPI under single driver. Could you be
> more specific how we break powernow-k8?
I haven't seen the if (!check_speedstep_cpu(cpu)) {...} onto
apci_cpufreq_cpu_init_acpi() indeed.
Therefore you are correct.
But it's funny to see that how acpi_cpufreq driver become
so Intel specific.
If AMD or any other vendors want to add their stuff
onto acpi_cpufreq, then should we accept their patches
as well?
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2006-08-03 16:11 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 [this message]
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
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=20060803161130.GL17014@poupinou.org \
--to=ducrot@poupinou.org \
--cc=alexey_y_starikovskiy@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox