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] dynamic chip support
Date: Fri, 25 May 2007 08:34:04 +0000	[thread overview]
Message-ID: <46569F7C.8000302@hhs.nl> (raw)
In-Reply-To: <461B7F5C.5080409@hhs.nl>

Jean Delvare wrote:
> Hi Hans,
> 
>> Some observations, in an ideal world this dyn chipsupport could replace most of 
>> the 5000 lines of code in prog/sensors/chips.c, however some chips seem to use 
>> non standard sysfs names <sigh> like remote_temp and zone_xxxxx, etc. I'm 
> 
> A Linux 2.6 driver creating a sysfs file named remote_temp? I can't
> believe that. Can you please double-check, and point me to it if it
> really exists? Some Linux 2.4 driver did that, I know, but the feature
> should have been renamed to temp2_input when the driver was ported to
> Linux 2.6.
> 

I might be getting / reading this wrong, but take a look at adm1021_features
in lib/chips.c there it still clearly states:
     { { SENSORS_ADM1021_REMOTE_TEMP, "remote_temp", NOMAP, NOMAP, R },
                                      ADM1021_SYSCTL_REMOTE_TEMP, VALUE(3), 0 },
     { { SENSORS_ADM1021_REMOTE_TEMP_HYST, "remote_temp_low",
...

I haven't looked at the actual 2.6 driver. If the 2.6 driver indeed calls it 
temp2_input, then how does libsensors know this??

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-05-25  8:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10 11:54 [lm-sensors] dynamic chip support Hans de Goede
2007-05-25  7:53 ` Jean Delvare
2007-05-25  8:34 ` Hans de Goede [this message]
2007-05-25 13:25 ` Jean Delvare

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=46569F7C.8000302@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.