RE: Patch for ospmd thermal gui

RE: Patch for ospmd thermal gui

[Grover, Andrew]

> From: Knut Neumann [mailto:knut.neumann-4bfl1RV3iZDOEhgYWvzSCYQuADTiUCJX@public.gmane.org] 
> as you suggested last year I made the ospmd_gui have a 
> thermal page. Now
> I found the time to clean the patch up and send it to you.

Thanks!

(BTW we are going to switch from the ACPI CA license to the BSD license,
is that OK with you?)

> I always thought to transparently export the acpi interface through
> ospmd/libpower. That is why I made one struct (PM_THERMAL_DATA) per
> zone. Now that seems plain wrong to me.
> 
> As I understand today you want ospmd to gather those 
> information needed
> for power management (policies) from /proc/acpi and export control of
> ospmd via libpower - is that right?

Yes. I'm assuming the user will be using a GUI-specific PM control panel
program, so my thought was that all these would act on the same power
policy by using libpower to talk to ospmd. This makes the interface
libpower exposes VERY IMPORTANT. It should not change once we lock it
down. I think at some point we need to review it (does it have enough
information? Too much?). IIRC we also are using internal data structures
in it, so we will probably want to fix that.

> In conclusion that would rather mean to have access to eg cooling
> mode/temperature (in ospmd _and_ libpower) via:
> 
> pm_set_thermal_cooling
> pm_get_thermal_cooling
> pm_get_thermal_temperature
> 
> to be able to either set cooling mode from the gui directly or have a
> policy in ospmd that eg switches cooling mode to active when a certain
> temperature is reached.

Well, cooling mode is only supposed to be specified by the user, so I
don't think ospmd would change it by itself. However, there is a lot of
room for ospmd to take the user's preference and then do the right thing
based on that. For example, what do we do when the battery gets low? If
the user has said to suspend the system when battery reaches 10%, then
ospmd needs to track that and make it happen at the right time.

Regards -- Andy


-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/

RE: Patch for ospmd thermal gui

[Knut Neumann]

Am Mon, 2003-03-31 um 20.36 schrieb Grover, Andrew:
> Thanks!

I should have mentioned that this patch is incremental to the other one
I sent to you, which added autotools support...

> (BTW we are going to switch from the ACPI CA license to the BSD license,
> is that OK with you?)

No problem. 

> Yes. I'm assuming the user will be using a GUI-specific PM control panel
> program, so my thought was that all these would act on the same power
> policy by using libpower to talk to ospmd. This makes the interface
> libpower exposes VERY IMPORTANT. 

Would you have the time to draw up an API for libpower (which maybe
should be named libospmd?!)? This could prevent some misunderstandings -
and I would happily start implementing it....

> Well, cooling mode is only supposed to be specified by the user, so I
> don't think ospmd would change it by itself. 

Hmmm..AFAIU ospmd is supposed to take care of user-specified power
policies, which are set through libpower: so I would think the user
should rather not be able to directly activate active cooling but it
should be done by ospmd in two cases: the user specified active cooling
when temperature reaches a certain point - or some (default) value is
reached which is assumed critical for passive cooling. 

> However, there is a lot of
> room for ospmd to take the user's preference and then do the right thing
> based on that. For example, what do we do when the battery gets low? If
> the user has said to suspend the system when battery reaches 10%, then
> ospmd needs to track that and make it happen at the right time.

Ok. I understand now that I somehow missed the point. It seems to be a
good idea to complete the design of the gui pm control panel or the
libpower API. Would you think you have some time in the near future to
do one of those? Otherwise I could do some work on such a gui program by
taking the small pm-control-applet which was pre-installed on my vaio
under windows and the existing gui as a start...though I would rather
like to do it in gnome/gtk since I am not that familiar with QT. 


-Knut
-- 
Knut Neumann <knut.neumann-4bfl1RV3iZDOEhgYWvzSCYQuADTiUCJX@public.gmane.org>
Physikalische Grundpraktika - Heinrich-Heine Universitaet Duesseldorf
Raum 25.33.01.63  -   Universitaetsstrasse 1   -  D-40225 Duesseldorf
fon: +49-211-81-11314                           fax: +49-211-81-13105











-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/

Re: RE: Patch for ospmd thermal gui

[Pavel Machek]

Hi!

> Would you have the time to draw up an API for libpower (which maybe
> should be named libospmd?!)? This could prevent some misunderstandings -
> and I would happily start implementing it....

libpower is *way* nicer name.
-- 
				Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...



-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/