RE: Changing temperature trip points

Edmund Rhudy
2002-11-03T22:09:43Z

My point is more that it might be better to assume that things won't
work. This isn't a sound driver. This is something that the life of
the computer depends on, and if somebody's processor melts down because
they didn't read some piece of kernel documentation that they didn't
even know existed, they're not likely to be particularly forgiving and
think "Oh, it was my fault for not realising that my hardware was
broken, I'll be more careful next time".

-----Original Message-----
From: Pavel Machek [mailto:pavel-+ZI9xUNit7I@public.gmane.org]
Sent: Sunday, 3 November 2002 5:03 PM
To: Edmund Rhudy
Cc: 'Dominik Brodowski'; 'Pavel Machek';
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [ACPI] Changing temperature trip points

Hi!

> See, now that I can understand. :)
>
> Anyway, let's see...having set temperatures to 60, 50 and 45 C
> respectively, and running a compile to move the core temperature up,
> the fan does in fact trigger at 45 C. Outstanding. I'll script it
> into changing them automatically at startup.
>
> Pavel also wrote the following:
>
> > I believe user should be clever enough to set polling rate manually.
>
> I wouldn't leave anything to the user unless it's extremely clear cut,

> particularly with the movement towards a more Windows-like Linux (see
> Bluecurve) that tries to soften the reality of Linux not being that
> friendly to the average schmuck.

No.

You only ever need to touch polling_frequency in case your hardware is
broken. If you are working around broken hardware,you'd better know what
you are doing.

Kernel is *not* meant to be user friendly. You can have your "broken
hardware setup wizard" in your distribution if you want, but not in
kernel.

Pavel
--
Casualities in World Trade Center: ~3k dead inside the building,
cryptography in U.S.A. and free speech in Czech Republic.