|
From: Thomas R. <tr...@su...> - 2006-11-22 12:35:03
|
On Tue, 2006-11-21 at 21:48 +0200, Shem Multinymous wrote: > Hi, > > > > >The TODO feature lists is: > > > > 2. Add kernel-space fan control override > > > > > > What do you mean? > > > > tp-fancontrol in kernel land, but with an ACPI-like interface. As if > > Lenovo/IBM had done things properly and given us 8-12 thermal zones with > > trip points and a system fan power resource in all of them. This sounds really nice. > > Interesting. Lot of work, though. And it will be a bit harder to > implement some wilder ideas like > http://thinkwiki.org/wiki/ACPI_fan_control_script#Ideas_for_improvement A common interface is really desirable. > Functionally, it seems easier to port tp-fancontrol to mlockall()ed > userspace C (or maybe Perl, if mlocFront-end desktop applications at least must nkall()ing it isn't too expensive). If specific userspace code is needed, shouldn't these things be a HAL plugin/module? HAL is AFAIK used by every distribution and is the way to go for future? Collecting thinkpad_x, thinkpad_y, asus, acer, whatever packages (which often tend to end up unmaintained in some years) is a pain. Access to a HAL fan/battery/AC/... interface (even better already abstracted in kernel if possible) should at least hide the fact there is a ThinkPad behind. There are KDE, Gnome, plain X, Konsole applications, if you need for every a ThinkPad (and/or other) specific applications or if of these applications need to implement ThinkPad (and/or other) specific functions we are lost. Holger wrote a cpufreq userspace HAL plugin and can comment better on this than me, whether a HAL fan plugin with possible TP specific extensions makes sense or can give a helping hand on this... Thomas |
