On Thu, 2007-08-09 at 01:58 -0400, Len Brown wrote:
> In response to the outcry after I deleted the trip-point
> overrides, here is how I think we can work-around
> thermal issues in a supportable way.
>
> In particular, this series should address the issues
> on Knut's AOpen Award system here:
> http://bugzilla.kernel.org/show_bug.cgi?id=8842
> and give us the hooks to address analogous issues in
> other systems.
>
> Please let me know what you think.
Thanks.
This is very much appreciated.
I like the idea of boot parameters, this avoids the seduction to build
tools on it and mis-use this as an official interface.
But where I like to see a sysfs interface for, is the passive trip point
and allow:
a) lowering passive trip points
b) let user define his own passive trip point if none
is provided by BIOS
I don't remember whether every trip point gets it's own sysfs file. If
yes, adding a passive_user file, default -1 and the normal passive file
where the current active passive trip point value is shown, is how I
think this could be done.
I know you hate it, because it's not explicitly stated in ACPI spec,
works around it a bit and so on.
But this one is:
1) safe (in respect to hardware and code)
2) a very mighty feature
Please let us implement the spec a little loose at this point, M$ is
also doing it at other parts. Let's get some fruits not always the
stones...
Thanks,
Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
