From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] THMC50 support for 2.6 (2nd revision)
Date: Sun, 08 Jul 2007 12:42:18 +0000 [thread overview]
Message-ID: <20070708144218.412d67aa@hyperion.delvare> (raw)
In-Reply-To: <20070702195448.2814dfb7.krzysztof.h1@wp.pl>
Hi Krzysztof,
On Fri, 06 Jul 2007 13:39:47 +0200, Krzysztof Helt wrote:
> I need help how to name the temperature 3 and 4. They are both on
> the MB. Do you have any standard for naming temperatures in the
> lmsensors lib (like CPU are always "Temp CPUx")?
Sensor names don't go into the library. The only place where you give
names to the sensors is in sensors.conf. As you're writing a dedicated
configuration file for your motherboard, you are free to choose
whatever names you like. You can look at other configuration files for
examples (etc/sensors.conf.eg or the ones in the wiki on
lm-sensors.org.)
> Thanks for the tip with hair-dryer.
Be careful when trying this. Electronic components don't like abrupt
temperature changes, so make sure that the air coming out of the
hair-dryer isn't too hot. If it's too hot, you'll need to find a way to
mix it with fresher air, or you might damage your hardware.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2007-07-08 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 17:54 [lm-sensors] [PATCH] THMC50 support for 2.6 (2nd revision) Krzysztof Helt
2007-07-04 9:36 ` Jean Delvare
2007-07-04 17:16 ` Krzysztof Helt
2007-07-05 12:29 ` Mark M. Hoffman
2007-07-06 10:01 ` Jean Delvare
2007-07-06 10:12 ` Hans de Goede
2007-07-06 11:39 ` Krzysztof Helt
2007-07-08 12:42 ` Jean Delvare [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070708144218.412d67aa@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.