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] A question regarding ASRock H55DE3 motherboard
Date: Wed, 17 Feb 2010 21:15:33 +0000	[thread overview]
Message-ID: <20100217221533.33699b9a@hyperion.delvare> (raw)
In-Reply-To: <4B7A403E.7000103@permonline.ru>

On Thu, 18 Feb 2010 01:08:04 +0500, Artem S. Tashkinov wrote:
> On 02/18/2010 12:19 AM, Jean Delvare wrote:
>  > This driver should be available. If it's not there, this suggests that
>  > you did not set CONFIG_SENSORS_ADT7473=m when building your kernel. You
>  > should have...
> 
> I will try to build this driver and report if it shows anything.

Note: last time I checked (long ago), the binary nvidia driver which
you appear to be using, did not let hwmon driver probe its I2C buses
for devices. So you might have to instantiate the chip yourself with:

# echo adt7473 0x2e > /sys/class/i2c-adapter/i2c-<N>/device/new_device

where <N> is the bus number of the i2c bus in question.

> (...)
> It looks like it's my own blunder: I have confused w83_2_627 to w83627 
> :) and taking into consideration ASRock's documentation my chip is 
> indeed made by Nuvoton and it's currently unsupported - I'm eagerly 
> awaiting patches to be merged.

Hmm, does the W832627 actually exist? I thought it was a typo.

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

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

  parent reply	other threads:[~2010-02-17 21:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16  6:50 [lm-sensors] A question regarding ASRock H55DE3 motherboard Artem S. Tashkinov
2010-02-17 19:19 ` Jean Delvare
2010-02-17 20:08 ` Artem S. Tashkinov
2010-02-17 21:15 ` Jean Delvare [this message]
2010-02-18 11:25 ` Artem S. Tashkinov
2010-02-19  9:52 ` Jean Delvare
2010-02-19 12:26 ` Artem S. Tashkinov

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=20100217221533.33699b9a@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.