All of lore.kernel.org
 help / color / mirror / Atom feed
From: udovdh@xs4all.nl (Udo van den Heuvel)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] new vt1211 driver: Can't access procfs/sysfs file
Date: Sun, 03 Dec 2006 12:33:59 +0000	[thread overview]
Message-ID: <4572C437.1050704@xs4all.nl> (raw)
In-Reply-To: <45728865.5020308@xs4all.nl>

Jean Delvare wrote:
> On Sun, 03 Dec 2006 12:13:50 +0100, Udo van den Heuvel wrote:
>> Jean Delvare wrote:
>>> are ignore statements for them in your configuration file. 
>> Sure. But not for the temperatures.
>> (...)
>> chip "vt1211-*" "vt8231-*"
>> #
>> #
>> #ignore in6
>> #set config 12
>> ignore in0
>> ignore in1
>> ignore temp1
>> ignore temp2
>> ignore temp4
>> ignore temp5
>> ignore temp6
>> ignore temp7
> 
> "No, Sir, I don't have ignore statements for temperatures. I swear!"
> 
> Tsss...

As you can see the situation was edited for temp3 which was the cpu temp
sensor. All other temp sesnors are of no interest at all.
So my answer should be read as 'not for the temperatures that are
interesting'. The Tsss could show a lack of something.
You are moving way off the focus of this quest which is very clear.

>> I just see that temp sensors might have been renumbered?
> 
> Yes, they have been, and the values have been changed as well, so the
> compute statements are different.

That's very nice to do! Why oh why keep something that works?
Where can I find the very simple knowledge to build new compute
statments, my only interesting hobby?

Udo


  parent reply	other threads:[~2006-12-03 12:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-03  8:18 [lm-sensors] new vt1211 driver: Can't access procfs/sysfs file for Udo van den Heuvel
2006-12-03 10:36 ` [lm-sensors] new vt1211 driver: Can't access procfs/sysfs file Jean Delvare
2006-12-03 10:41 ` Udo van den Heuvel
2006-12-03 11:04 ` Jean Delvare
2006-12-03 11:13 ` Udo van den Heuvel
2006-12-03 12:26 ` Jean Delvare
2006-12-03 12:33 ` Udo van den Heuvel [this message]
2006-12-03 13:42 ` Jean Delvare
2006-12-03 14:34 ` Udo van den Heuvel

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=4572C437.1050704@xs4all.nl \
    --to=udovdh@xs4all.nl \
    --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.