From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] lm-sensors 3.0.0-rc1 has been released!
Date: Fri, 19 Oct 2007 20:18:02 +0000 [thread overview]
Message-ID: <471910FA.4030802@hhs.nl> (raw)
In-Reply-To: <20070925233316.7afaa297@hyperion.delvare>
Jean Delvare wrote:
> Hi Hans,
>
> On Wed, 26 Sep 2007 23:02:31 +0200, Hans de Goede wrote:
>> Excellent work Jean! I've given this a test run on all my systems / test rigs
>> and it works great everywhere. I'll create patches for ksensors, gkrellm, and
>> gome's sensors-applet as time permits. I'm afraid this will take a while as
>> currently I'm very busy with stuff regarding the upcoming Fedora 8.
>
> Any news on this? I am more or less waiting for this to happen before
> we can release lm-sensors 3.0.0 final.
>
Okay,
I've ported my first application over: gkrellm. gkrellm only uses the main
featuree (_input values) so I instinctively wrote this:
while ((feature = sensors_get_features(name, &nr1))) {
/* ..... */
result = sensors_get_value(name, feature->number, &val);
Which to my surprise doesn't work I now know this should be:
while ((feature = sensors_get_features(name, &nr1))) {
/* ..... */
result = sensors_get_value(name,
sensors_get_subfeature(name, feature,
SENSORS_SUBFEATURE_IN_INPUT),
feature->number, &val);
Which must be put in a switch statement on feature->type to put in
SENSORS_SUBFEATURE_IN_INPUT / SENSORS_SUBFEATURE_FAN_INPUT /
SENSORS_SUBFEATURE_TEMP_INPUT
Ideally my first naive code should just work for simple applications which only
want to read the main / _input feature, I haven't checked yet, but I think
making my initial code work, doesn't match well with the current libsensors
structure, so how about adding an "int input_subfeature_number" to the
sensors_feature struct, so that my original code will work like this:
while ((feature = sensors_get_features(name, &nr1))) {
/* ..... */
result = sensors_get_value(name,
feature->input_subfeature_number, &val);
Or alternatively a sensors_get_main_value(name, feature, &val) function?
Besides that adding a define to sensors.h which can be tested to find out
against which libsensors version code is compiling would be a good idea too.
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2007-10-19 20:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 21:33 [lm-sensors] lm-sensors 3.0.0-rc1 has been released! Jean Delvare
2007-09-25 21:45 ` Philip Edelbrock
2007-09-26 21:02 ` Hans de Goede
2007-09-27 14:35 ` Jean Delvare
2007-09-27 14:42 ` Jean Delvare
2007-09-27 17:53 ` Henrique de Moraes Holschuh
2007-09-28 17:07 ` Jean Delvare
2007-09-28 20:13 ` Henrique de Moraes Holschuh
2007-09-29 13:39 ` Jean Delvare
2007-09-30 0:56 ` Henrique de Moraes Holschuh
2007-09-30 11:54 ` Jean Delvare
2007-09-30 12:10 ` Jean Delvare
2007-09-30 14:54 ` Henrique de Moraes Holschuh
2007-10-03 10:36 ` Jean Delvare
2007-10-03 11:38 ` Henrique de Moraes Holschuh
2007-10-04 9:45 ` Jean Delvare
2007-10-04 12:49 ` Henrique de Moraes Holschuh
2007-10-04 13:42 ` Jean Delvare
2007-10-07 11:21 ` Axel Thimm
2007-10-17 21:44 ` Jean Delvare
2007-10-18 7:17 ` Hans de Goede
2007-10-18 8:18 ` Aurelien Jarno
2007-10-19 14:46 ` Jean Delvare
2007-10-19 20:18 ` Hans de Goede [this message]
2007-10-20 18:13 ` Jean Delvare
2007-10-20 22:41 ` Hans de Goede
2007-10-21 19:08 ` Jean Delvare
2007-10-21 19:13 ` Hans de Goede
2007-10-21 21:12 ` Jean Delvare
2007-10-22 7:06 ` Hans de Goede
2007-10-22 7:48 ` Jean Delvare
2007-10-22 8:13 ` Hans de Goede
2007-10-22 8:23 ` Jean Delvare
2007-10-22 9:40 ` Hans de Goede
2007-10-22 11:55 ` Jean Delvare
2007-10-22 13:15 ` Hans de Goede
2007-10-22 13:55 ` Jean Delvare
2007-10-22 19:27 ` Hans de Goede
2007-10-22 22:25 ` Aurelien Jarno
2007-10-24 15:30 ` Jean Delvare
2007-10-24 17:09 ` Hans de Goede
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=471910FA.4030802@hhs.nl \
--to=j.w.r.degoede@hhs.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.