[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <464B4911.4050903@free.fr>
Date: Wed, 16 May 2007 20:10:25 +0200
From: Goulven Guillard <lecotegougdelaforce@...e.fr>
To: Chuck Ebbert <cebbert@...hat.com>
CC: Maciej Rutecki <maciej.rutecki@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
lenb@...nel.org
Subject: Re: 2.6.22-rc1-mm1 [cannot change thermal trip points]
Le 05/16/2007 07:47 PM, Chuck Ebbert a déclaré :
> Gitweb: http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=11ccc0f249cb01a129f54760b8ff087f242935d4
> Commit: 11ccc0f249cb01a129f54760b8ff087f242935d4
> Parent: de46c33745f5e2ad594c72f2cf5f490861b16ce1
> Author: Len Brown <len.brown@...el.com>
> AuthorDate: Mon Apr 30 22:36:01 2007 -0400
> Committer: Len Brown <len.brown@...el.com>
> CommitDate: Mon Apr 30 22:36:01 2007 -0400
>
> ACPI: thermal trip points are read-only
Should one understand that it IS a wanted behaviour ?
Isn't it the DSDT job (which is kernel-accessible, or isn't it ?) to
communicate trip_points to ACPI thermal zone ?
Isn't OSPM managing thermal zone ?
(http://acpi.sourceforge.net/documentation/thermal.html)
PS : Sorry for all these (maybe stupid) questions, but I think I
remember that changing trip_points had an effect on a (DSDT-bugged)
laptop I used to use, and I'd like to understand...
PPS : Sorry also for the english mistakes or approximations...
--
~~
|Oo| La banquise fond !!! Adoptez un pingouin...
/|\/|\
|__| => http://doc.ubuntu-fr.org/
^__^
~~~| |~~~
-
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/
Powered by blists - more mailing lists