All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] xsensors ported to the future libsensors
Date: Mon, 23 Jul 2007 17:14:46 +0000	[thread overview]
Message-ID: <46A4E206.7090507@hhs.nl> (raw)
In-Reply-To: <20070720213455.644b5f50@hyperion.delvare>

Jean Delvare wrote:
> On Sun, 22 Jul 2007 20:06:02 +0200, Hans de Goede wrote:
>> Jean Delvare wrote:
>>> I'm curious how gnome sensors-applet and gkrellm managed to use the
>>> current libsensors without chip-specific code at all, as it definitely
>>> wasn't designed to be used that way.
>> They both basically have there own version of sensors_get_feature_type, both 
>> assuming to be running on a 2.6 kernel, and thus have sysfs interface standard 
>> feature names.
> 
> I'm surprised, as the feature names exposed by libsensors are the old
> (non-standard) ones, even for 2.6 kernels. The mapping to the new
> symbols is internal as far as I can see. "sensors -u" returns the old
> feature names. So I guess they assume that old names are somewhat
> standard, and it doesn't work for all drivers?
> 

Correct, but gkrellm does for example contain code to also work with the 
via686a 2.0V style volt feature names

Regards,

Hans

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

      parent reply	other threads:[~2007-07-23 17:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20 19:34 [lm-sensors] xsensors ported to the future libsensors Jean Delvare
2007-07-20 20:33 ` Hans de Goede
2007-07-22 15:36 ` Jean Delvare
2007-07-22 18:06 ` Hans de Goede
2007-07-23 16:58 ` Jean Delvare
2007-07-23 17:14 ` Hans de Goede [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=46A4E206.7090507@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.