All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Missing thmc50 support in sensors
Date: Sun, 09 Sep 2007 11:17:28 +0000	[thread overview]
Message-ID: <20070909131728.58edb10f@hyperion.delvare> (raw)
In-Reply-To: <20070906130600.028cf7f5@hyperion.delvare>

Hi Krzysztof,

On Sun, 9 Sep 2007 10:42:20 +0200, Krzysztof Helt wrote:
> On Thu, 6 Sep 2007 13:06:00 +0200 Jean Delvare wrote:
> > In ticket #2250, someone using your new thmc50 driver is complaining
> > about the lack of pretty-print support in "sensors":
> > 
> > http://www.lm-sensors.org/ticket/2250#comment:2
>
> The current lmsensors2 displays all information it can get
> from 2.6 driver. The only problem is the lmsensors2 cannot
> get information about non-existing entries.
> 
> How can I hide entries (like die_code) which do not exist
> in the 2.6 driver?

With the current code, you can't because "sensors" has no pretty-print
routine for the thmc50/adm1022. So it falls back to the "unknown chip"
printing routine, which blindly trusts the feature list provided by
libsensors. This somewhat worked for Linux 2.4 drivers but no longer
for Linux 2.6 drivers, as you found out.

The solution is to write a pretty-print routine for the thmc50/adm1022.
Or more simply, copy and paste a similar one (for example print_lm63)
and change the symbols to the THMC50 ones. In this custom routine you
can simply omit the error messages for features which you now might be
missing for the Linux 2.6 driver.

-- 
Jean Delvare

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

  parent reply	other threads:[~2007-09-09 11:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06 11:06 [lm-sensors] Missing thmc50 support in sensors Jean Delvare
2007-09-09  8:42 ` Krzysztof Helt
2007-09-09 11:17 ` Jean Delvare [this message]
2007-09-09 14:30 ` Krzysztof Helt
2007-09-17 11:25 ` Jean Delvare
2007-09-17 12:28 ` Krzysztof Helt
2007-09-17 14:00 ` Jean Delvare
2007-09-19 12:01 ` Philippe Michiels
2007-09-19 13:31 ` Krzysztof Helt

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=20070909131728.58edb10f@hyperion.delvare \
    --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.