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 14:34:55 +0000	[thread overview]
Message-ID: <4572E08F.2000005@xs4all.nl> (raw)
In-Reply-To: <45728865.5020308@xs4all.nl>

Jean Delvare wrote:
>> The Tsss could show a lack of something.
>> You are moving way off the focus of this quest which is very clear.
> 
> It looks like you are missing a very important point here. You are the
> one asking for help. I am the one providing the help FOR FREE, on my
> SPARE TIME. The least you can do is make it easy for me, provide
> correct answers to my questions, and assist as much as you can, instead
> of waiting for me to do all the work based on incomplete information.

Sure. I agree completely.
On the other hand you can be sure that in most sensors.conf there will
be ignore statemnts so that the abuser is not overwhelmed with sensors
giving nonsense values.
The sensors that /made/ sense had no ignore statments in my config.
Of coure I was not so clear.

> point I still don't know what was that system. 2.4 kernel? Or 2.6 with
> Lars Ekman's unofficial driver?

2.6 on FC6 with Lars' driver (and various changes in the recent past).

> Why did you upgrade your system if it was working?

To keep up. It is routine. Vt1211 would be one of the reasons to
actually gain something. `Official` support. No more patching to make
things work.

> (Seriously, if you're not happy with what we do, feel tree to join the
> development team and show us how to make things better. I'm eager to
> improve. There's plenty of work for everyone interested.)

lm-sensors was not the cause. it was the new driver and associated
expectations ('drop-in replacement')

>> Where can I find the very simple knowledge to build new compute
>> statments, my only interesting hobby?

[..]

> Most probably, you don't actually
> need to change the formula, just replace "compute temp3" by "compute
> temp1".

Done.


      parent reply	other threads:[~2006-12-03 14:34 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
2006-12-03 13:42 ` Jean Delvare
2006-12-03 14:34 ` Udo van den Heuvel [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=4572E08F.2000005@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.