From: support@ocg.ca (Michelle Dupuis)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] question about vt1211
Date: Fri, 19 Jan 2007 21:08:58 +0000 [thread overview]
Message-ID: <00b301c73c0e$098eca30$65fe1fac@ocg.ca> (raw)
In-Reply-To: <191fb4ca0701190725j2620de3dvd521e23c690e72e@mail.gmail.com>
On the same topic...(this answer may address your question too)
I just upgraded my kernel from from 2.6.17 to 2.6.18, and my old vt1211.c
broke. Although it compiles and runs, my cpu temp is now stuck at 68'C
(normally runs half that). Under 2.6.17 it showed 35'C approx.
Is there a newer vt1211 I can download somewhere?
Thanks,
Michelle
-----Original Message-----
From: lm-sensors-bounces@lm-sensors.org
[mailto:lm-sensors-bounces at lm-sensors.org] On Behalf Of Juerg Haefliger
Sent: Friday, January 19, 2007 10:25 AM
To: Sasha Raykhman
Cc: LM Sensors
Subject: Re: [lm-sensors] question about vt1211
Hi Sasha,
For future questions, please cc the lm-sensors mailing list since other
people might be interested as well.
> I compiled the driver and successfully installed the module on my
> distribution (TimeSys 2.6.17) . I read the document I found in
> 2.6.19, but it didn't give me the idea on how to call driver functions
> from user level application.
I'm not familiar with TimeSys but from the name I'm assuming your're running
a 2.6.17 kernel. The official vt1211 driver is not part of this kernel, it
got added later with 2.6.19. Are you using Lars Ekmans' driver? If so, you
should switch to 2.6.19 or later and use the official vt1211 driver that
comes with the kernel.
Like all hwmon drivers, the vt1211 driver creates a bunch of sysfs files
which are used to exchange data between the driver and user-space processes.
After loading the official driver, check /sys/class/hwmon/vt1211. It
contains a bunch of files that you can access using regular read() and
write() file operations to retrieve data from the driver (like temps and fan
RPMs) or write data to the driver (like thermal thresholds).
Please check Documentation/hwmon/sysfs-interface and vt1211 for an
explanation of how to interpret the various files and their content.
The standard way is to use a tool called 'sensors' which is part of the
lm-sensors package. It reads these files, manipulates the data according to
some rules specified in /etc/sensors.conf and displays them. Check it out...
> VIA Web site has utility VIA_SystemHealth, but they don't provide
> source code as a reference for developers. Could you please give me
> some idea on how to find API to the driver.
VIA's tool doesn't work with the 2.6.19 vt1211 driver, it is tailored toward
the old unofficial driver.
...juerg
> Thanks for the help.
>
> -- sasha
>
_______________________________________________
lm-sensors mailing list
lm-sensors at lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2007-01-19 21:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 15:25 [lm-sensors] question about vt1211 Juerg Haefliger
2007-01-19 21:08 ` Michelle Dupuis [this message]
2007-01-19 22:19 ` Sasha Raykhman
2007-01-19 22:24 ` Michelle Dupuis
2007-01-20 15:47 ` Juerg Haefliger
2007-01-20 15:57 ` Juerg Haefliger
2007-01-22 18:11 ` Sasha Raykhman
2007-01-22 18:22 ` Juerg Haefliger
2007-01-23 0:51 ` Sasha Raykhman
2007-01-23 8:13 ` Jean Delvare
2007-01-23 12:56 ` Mark M. Hoffman
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='00b301c73c0e$098eca30$65fe1fac@ocg.ca' \
--to=support@ocg.ca \
--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.