From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Power mgmt / CPUFREQ on Via C7 (Esther)
Date: Tue, 02 Jan 2007 19:18:33 +0100 [thread overview]
Message-ID: <459AA1F9.3040701@interia.pl> (raw)
In-Reply-To: <20070102173601.GD7656@redhat.com>
> > Hi
> >
> > I have just bought a nice little sbc mainboard with a Via C7 cpu. It run
> > Centos with stock kernel 2.6.19.1 that I downloaded and installed a few
> > days ago.
> > But cpufreq does not work.
> >
> > Can I in some way help with testing/debugging the cpufreq driver (centrino
> > or longhaul?) for this cpu?
>
> The C7 works fine with acpi-cpufreq if the correct BIOS tables are present.
> Support *could* be added to speedstep-centrino to use hardcoded tables
> for these CPUs for systems where the BIOSes lack them, but hasn't been
> done yet.
>
> Given speedstep-centrino is due to be obsoleted by acpi-cpufreq at some stage,
> the feature of using hardcoded tables probably needs to be added to
> acpi-cpufreq at some point too.
>
> Dave
>
Beauty of "Enhanced PowerSaver" is in that hardcoded tables are not necessary.
Would be very easy to add ACPI independent driver for these CPU's. If somebody
would test it then I can try.
What do You think?
Rafa³
----------------------------------------------------------------------
Jestes kierowca? To poczytaj! >>> http://link.interia.pl/f199e
next prev parent reply other threads:[~2007-01-02 18:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 12:17 Power mgmt / CPUFREQ on Via C7 (Esther) jorgen
2007-01-02 17:36 ` Dave Jones
2007-01-02 18:18 ` Rafał Bilski [this message]
2007-01-02 23:19 ` Dave Jones
2007-01-03 23:10 ` Jorgen
2007-01-02 18:55 ` Len Brown
2007-01-04 12:37 ` Jorgen
-- strict thread matches above, loose matches on Subject: below --
2007-01-02 22:16 jorgen
2007-01-02 22:27 ` Dave Jones
2007-01-03 10:22 jorgen
2007-01-03 20:41 ` Len Brown
2007-01-04 10:06 jorgen
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=459AA1F9.3040701@interia.pl \
--to=rafalbilski@interia.pl \
--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.