From: Roberto Gordo Saez <roberto.gordo@gmail.com>
To: "Langsdorf, Mark" <mark.langsdorf@amd.com>, cpufreq@lists.linux.org.uk
Subject: Re: Voltage tweaking in powernow_k8
Date: Mon, 16 Apr 2007 17:25:52 +0200 [thread overview]
Message-ID: <46239583.67d3ffa6.271c.2ed5@mx.google.com> (raw)
In-Reply-To: <1449F58C868D8D4E9C72945771150BDF02076D07@SAUSEXMB1.amd.com>
On Mon, Apr 16, 2007 at 08:55:38AM -0500, Langsdorf, Mark wrote:
> AMD policy is that the ACPI values must be used. I
> can't support a patch that overrides the ACPI values.
>
> I have no objection to it being in the code, but I
> can't support it.
Hi, thanks for replying.
I understand your position about this. Please, correct me if I'm
giving a wrong interpretation to your message; in the way I read it,
you are unable to support those changes (because of your position at
AMD you are required to strictly follow the policy), but you could
live with those changes provided that your name is not attached to
them...
Admittely, it is not such an elegant solution, but people are indeed
doing other hacks anyway, like statically overriding the ACPI table
with a hacked DSDT at kernel compile time (distributions like gentoo
have HOWTOs for this). I'm not sure if this would be a preferred
approach, but it does look even uglier to me. If you have any
suggestion or alternative proposal, I would be interested in your
opinion.
It may be a good idea to print warnings when the parameter is used,
to clearly state the unsupported and potentally dangerous effect of
the parameter (though it would not be enough to change your view,
I guess...).
next prev parent reply other threads:[~2007-04-16 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 17:18 Voltage tweaking in powernow_k8 Roberto Gordo Saez
2007-04-16 13:55 ` Langsdorf, Mark
2007-04-16 15:25 ` Roberto Gordo Saez [this message]
2007-04-20 18:35 ` Langsdorf, Mark
2007-04-20 18:55 ` Dave Jones
2007-04-20 21:03 ` Roberto Gordo Saez
2007-04-20 21:57 ` Dave Jones
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=46239583.67d3ffa6.271c.2ed5@mx.google.com \
--to=roberto.gordo@gmail.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=mark.langsdorf@amd.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.