All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] new vt1211 driver: Can't access procfs/sysfs file
Date: Sun, 03 Dec 2006 12:26:45 +0000	[thread overview]
Message-ID: <20061203132645.3b06d358.khali@linux-fr.org> (raw)
In-Reply-To: <45728865.5020308@xs4all.nl>

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...

> > BTW, I hope
> > you started from the default configuration file shipped with lm_sensors
> > 2.10.1 and not an older version, as it was significantly updated to
> > properly support the new Linux 2.6 version of the driver.
> 
> And go though all of that config stuff that does not make sense for my
> board?

Or you can be smart and only copy the vt1211 section. It's up to you.

> 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.

-- 
Jean Delvare


  parent reply	other threads:[~2006-12-03 12:26 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 [this message]
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

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=20061203132645.3b06d358.khali@linux-fr.org \
    --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.