All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Albert Cahalan <albert@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lm sensors sysfs file structure
Date: Thu, 27 Mar 2003 15:10:27 -0800	[thread overview]
Message-ID: <20030327231027.GC1687@kroah.com> (raw)
In-Reply-To: <1048806052.10675.4440.camel@cube>

On Thu, Mar 27, 2003 at 06:00:51PM -0500, Albert Cahalan wrote:
> Greg KH writes:
> 
> > temp_max[1-3]   Temperature max value.
> >                 Fixed point value in form XXXXX and
> >                 should be divided by
> >                 100 to get degrees Celsius.
> >                 Read/Write value.
> 
> Celsius can go negative, which may be yucky
> and hard to test. Kelvin generally doesn't
> suffer this problem. (yeah, yeah, quantum stuff...)

Wow, only 4 hours before someone mentioned Kelvin, I think I lost a bet
with someone :)

Seriously, let the value go negative, no problem.  As long as it isn't
floating point input which has to be parsed by the kernel.  That's all I
care about.

> Getting temperature display into "top" would sure
> be nice, but not if that means requiring a library
> that almost nobody has installed. It's good to give
> apps a simple way to get CPU temperature, including
> per-CPU data for SMP systems when available.

libsensors is installed on almost all distros these days.

> Info about sensor quality would be good. For example,
> my CPU measures temperature in 4-degree increments
> and is not calibrated.

I doubt the kernel driver knows this information.

thanks,

greg k-h

  reply	other threads:[~2003-03-27 23:00 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27 23:00 lm sensors sysfs file structure Albert Cahalan
2003-03-27 23:10 ` Greg KH [this message]
2003-03-28  7:21   ` Martin Schlemmer
2003-03-28  7:40     ` Greg KH
2005-05-19  6:23       ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2003-04-03 21:19 Grover, Andrew
2005-05-19  6:23 ` Grover, Andrew
2003-04-14 15:16 ` Patrick Mochel
2005-05-19  6:23   ` Patrick Mochel
2003-03-25  8:53 i2c driver changes for 2.5.66; adding w83781d support Martin Schlemmer
2003-03-25 17:56 ` Greg KH
2005-05-19  6:23   ` w83781d i2c driver updated for 2.5.66 (without sysfs support) Martin Schlemmer
2005-05-19  6:23     ` Jan Dittmer
2005-05-19  6:23       ` Greg KH
2005-05-19  6:23         ` Mark Studebaker
2003-03-26 22:52           ` lm sensors sysfs file structure Greg KH
2005-05-19  6:23             ` Greg KH
2003-03-27 10:46             ` Jan Dittmer
2005-05-19  6:23               ` Jan Dittmer
2003-03-27 10:50               ` Martin Schlemmer
2005-05-19  6:23                 ` Martin Schlemmer
2003-03-27 12:27                 ` Jan Dittmer
2005-05-19  6:23                   ` Jan Dittmer
2003-03-27 12:33                   ` Martin Schlemmer
2005-05-19  6:23                     ` Martin Schlemmer
2003-03-27 13:05                     ` Jan Dittmer
2005-05-19  6:23                       ` Jan Dittmer
2003-03-27 13:31                       ` Jean Delvare
2005-05-19  6:23                         ` Jean Delvare
2003-03-27 17:16                         ` Mark M. Hoffman
2005-05-19  6:23                           ` Mark M. Hoffman
2003-03-27 17:25               ` Greg KH
2005-05-19  6:23                 ` Greg KH
2003-03-27 18:06                 ` Jan Dittmer
2005-05-19  6:23                   ` Jan Dittmer
2003-03-27 18:13                   ` Greg KH
2005-05-19  6:23                     ` Greg KH
2003-03-30 19:23                 ` Pavel Machek
2005-05-19  6:23                   ` Pavel Machek
2003-04-01  6:44                   ` Greg KH
2005-05-19  6:23                     ` Greg KH
2003-04-01 20:22                     ` Pavel Machek
2005-05-19  6:23                       ` Pavel Machek
2003-04-01 23:27                     ` Dave Jones
2005-05-19  6:23                       ` Dave Jones
2003-04-03  0:28                       ` Greg KH
2005-05-19  6:23                         ` Greg KH
2003-04-03 10:49                         ` Dave Jones
2005-05-19  6:23                           ` Dave Jones
2003-04-03 18:43                           ` Dominik Brodowski
2005-05-19  6:23                             ` Dominik Brodowski
2003-03-27 18:40             ` Jan Dittmer
2005-05-19  6:23               ` Jan Dittmer
2003-03-27 18:52               ` Greg KH
2005-05-19  6:23                 ` Greg KH
2003-03-27 18:17                 ` Patrick Mochel
2005-05-19  6:23                   ` Patrick Mochel
2003-03-27 18:57                 ` Jan Dittmer
2003-03-27 19:15                 ` Martin Schlemmer
2005-05-19  6:23                   ` Martin Schlemmer
2003-03-27 19:25                   ` Greg KH
2005-05-19  6:23                     ` Greg KH
2003-03-27 19:42             ` Greg KH
2005-05-19  6:23               ` Greg KH
2003-03-27 20:32               ` Jan Dittmer
2005-05-19  6:23                 ` Jan Dittmer
2003-03-27 21:53                 ` Greg KH
2005-05-19  6:23                   ` Greg KH
2003-03-27 22:23                   ` Mark M. Hoffman
2005-05-19  6:23                     ` Mark M. Hoffman
2003-03-28  6:05                   ` Martin Schlemmer
2005-05-19  6:23                     ` Martin Schlemmer
2003-03-28 18:34             ` Pavel Machek
2005-05-19  6:23               ` Pavel Machek

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=20030327231027.GC1687@kroah.com \
    --to=greg@kroah.com \
    --cc=albert@users.sourceforge.net \
    --cc=linux-kernel@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.