From: "Corentin Chary" <corentin.chary@gmail.com>
To: "Thomas Renninger" <trenn@suse.de>
Cc: "Tom Hughes" <tom@compton.nu>,
acpi4asus-user@lists.sourceforge.net,
"Dave Jones" <davej@redhat.com>,
"Cristiano Prisciandaro" <cristiano.p@solnet.ch>,
linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org
Subject: Re: [Acpi4asus-user] [PATCH 1/1] cpufreq: eeepc 900 frequency scaling driver
Date: Mon, 24 Nov 2008 17:41:03 +0100 [thread overview]
Message-ID: <71cd59b00811240841j69451aafje5cbb5204dbff2e5@mail.gmail.com> (raw)
In-Reply-To: <200811241736.53067.trenn@suse.de>
On Mon, Nov 24, 2008 at 5:36 PM, Thomas Renninger <trenn@suse.de> wrote:
> On Monday 24 November 2008 04:13:24 pm Thomas Renninger wrote:
>> On Monday 24 November 2008 10:38:58 am Tom Hughes wrote:
>> > Cristiano Prisciandaro wrote:
>> > > From: Cristiano Prisciandaro <cristiano.p@solnet.ch>
>> > >
>> > > The bios of the eeepc 900 exposes an acpi method that allows clocking
>> > > the cpu to 630/900 MHz. This driver allows controlling the frequency
>> > > switch through the cpufreq subsystem.
>> >
>> > I should perhaps add at this point that I have an alternative patch
>> > based on Cristiano's code, which adds this cpufreq driver to the
>> > existing eeepc-laptop module rather than creating a separate module for
>> > it.
>> >
>> > Personally I'm quite happy with either solution so I'll leave it to you
>> > to decide what is the best way to go, but my patch is available if you
>> > want it.
>>
Why not just modprobe p4-clockmod ?
It already has all we want and works perfectly well.
next prev parent reply other threads:[~2008-11-24 16:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 15:27 Cristiano Prisciandaro
2008-11-23 18:04 ` Pavel Machek
2008-12-02 16:15 ` Matthew Garrett
2008-12-02 20:14 ` Pavel Machek
2009-03-16 4:24 ` Len Brown
2009-03-16 8:29 ` Pavel Machek
2009-03-17 8:30 ` Fabio Comolli
2009-03-17 8:59 ` Fabio Comolli
2008-11-24 9:38 ` Tom Hughes
2008-11-24 15:13 ` Thomas Renninger
2008-11-24 16:36 ` Thomas Renninger
2008-11-24 16:41 ` Corentin Chary [this message]
2008-11-24 16:48 ` [Acpi4asus-user] " Tom Hughes
2008-11-24 16:58 ` Corentin Chary
2008-11-24 17:07 ` Tom Hughes
2008-11-24 16:46 ` Tom Hughes
2008-11-24 23:02 ` Cristiano Prisciandaro
2009-04-05 7:43 ` [Acpi4asus-user] " Corentin Chary
2009-04-05 10:20 ` Matthew Garrett
2009-04-05 11:39 ` Grigori Goronzy
2008-11-24 16:39 ` Tom Hughes
2008-11-24 19:09 ` Cristiano Prisciandaro
2008-12-03 19:26 ` Tom Hughes
2008-12-04 1:57 ` Thomas Renninger
2008-12-05 23:05 ` Tom Hughes
2008-12-06 16:35 ` Matthew Garrett
2008-12-07 15:55 ` Tom Hughes
2008-12-09 12:36 ` Pavel Machek
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=71cd59b00811240841j69451aafje5cbb5204dbff2e5@mail.gmail.com \
--to=corentin.chary@gmail.com \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=cpufreq@vger.kernel.org \
--cc=cristiano.p@solnet.ch \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tom@compton.nu \
--cc=trenn@suse.de \
/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
all inboxes | Powered by JetHome®