linux-kernel - Re: [PATCH 1/1] cpufreq: eeepc 900 frequency scaling driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <b637ec0b0903170159u761b626ifda927925a723e0e@mail.gmail.com>
Date:	Tue, 17 Mar 2009 09:59:17 +0100
From:	Fabio Comolli <fabio.comolli@...il.com>
To:	Pavel Machek <pavel@....cz>
Cc:	Len Brown <lenb@...nel.org>, Matthew Garrett <mjg@...hat.com>,
	Cristiano Prisciandaro <cristiano.p@...net.ch>,
	Dave Jones <davej@...hat.com>, cpufreq@...r.kernel.org,
	linux-kernel@...r.kernel.org, tom@...pton.nu
Subject: Re: [PATCH 1/1] cpufreq: eeepc 900 frequency scaling driver

Well, replying to myself: it doesn't even compile with CONFIG_CPU_FREQ=n

On Tue, Mar 17, 2009 at 9:30 AM, Fabio Comolli <fabio.comolli@...il.com> wrote:
> Well, I see that this thread has resumed after three months of being idle.
> Is there a chance that either Cristiano's or Tom's version can be included?
>
> By the way, I currently run my eeepc 900 with cpufreq disabled.
> Looking at the patch, with Tom's mods to eeepc_laptop I could do the
> same, am I right? I see only an include for cpufreq.h and nothing
> else.
>
> Thanks,
> Fabio
>
>
>
> On Mon, Mar 16, 2009 at 9:29 AM, Pavel Machek <pavel@....cz> wrote:
>> On Mon 2009-03-16 00:24:18, Len Brown wrote:
>>>
>>> On Tue, 2 Dec 2008, Pavel Machek wrote:
>>>
>>> > On Tue 2008-12-02 16:15:21, Matthew Garrett wrote:
>>> > > On Sun, Nov 23, 2008 at 07:04:09PM +0100, Pavel Machek wrote:
>>> > >
>>> > > > Is this really needed? Could we simply talk to the cpu directly,
>>> > > > without help of ACPI?
>>> > >
>>> > > No. The ACPI write ends up talking to the embedded controller and some
>>> > > io ports.
>>> >
>>> > Oops... I always knew that eee-s are broken by design (reporting
>>> > battery percent as mWh, etc...) but I did not realize how bad it
>>> > is. (ACPI has perfectly standard cpu frequency scaling interface, even
>>> > if it is not used too often these days....)
>>>
>>> Huh?
>>>
>>> What cpufreq driver is deployed more broadly than acpi-cpufreq?
>>> AFAIK, Linux uses it on nearly every ACPI compliant Intel-based
>>> system that has frequency scaling.
>>
>> Problem seems to be that eee uses custom ACPI methods
>> (switch_to_fast_clock(0/1)-like), not anything acpi-cpufreq could
>> drive... Broken by design :-(.
>>                                                                        Pavel
>> --
>> (english) http://www.livejournal.com/~pavelmachek
>> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@...r.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at  http://www.tux.org/lkml/
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/