From: Nebojsa Trpkovic <trx.lists@gmail.com>
To: cpufreq@lists.linux.org.uk
Subject: Re: voltage tables
Date: Thu, 11 Oct 2007 17:43:32 +0200 [thread overview]
Message-ID: <470E44A4.5060207@gmail.com> (raw)
In-Reply-To: <f8o4nh$u2o$1@sea.gmane.org>
Wes Felter wrote:
> Len Brown wrote:
>> On Monday 30 July 2007 19:04, markus reichelt wrote:
>>> Hi,
>>>
>>> just a thought.... with more and more people wondering why cpufreq
>>> doesn't work on their over/underclocked systems, what about offering
>>> the possibility to use static (and thus easily tweakable) voltage
>>> tables instead of/parallel to the ACPI-approach?
>
> [snip]
>
>> Going forward, I believe that the hardware guys have no plans to
>> maintain any sort of reasonable compatibility or even straightforward
>> decoding of the bit pattern that gets written to PERF_CTL --
>> so the reason that speedstep-centrino and its hard-coded tables
>> became deprecated will be even more true in the future.
>
> User-provided tables != hard-coded tables. What if acpi-cpufreq dumped
> the ACPI table in some semi-human-readable format and then allowed the
> user to tweak it (by guessing, since the hardware is undocumented) and
> then push the tweaked table back into the driver at runtime? The driver
> would still not contain any tables and thus the old speedstep-centrino
> maintenance problem would not exist.
>
> There is a patch for speedstep-centrino that adds an op_points_table
> file in sysfs; it could be ported to acpi-cpufreq.
>
> http://gentoo-wiki.com/HOWTO_Undervolt_a_Pentium_M_CPU#Getting_the_current_voltage_settings
>
any info about eventual acpi-cpufreq port?
I've found this:
http://gentoo-wiki.com/HOWTO_Fix_Common_ACPI_Problems
but was unable to find any FID/VID table in DSDT... :(
prev parent reply other threads:[~2007-10-11 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 23:04 voltage tables markus reichelt
2007-07-31 2:41 ` Len Brown
2007-07-31 19:56 ` Wes Felter
2007-10-11 15:43 ` Nebojsa Trpkovic [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=470E44A4.5060207@gmail.com \
--to=trx.lists@gmail.com \
--cc=cpufreq@lists.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.