From: Phillip Susi <psusi-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Identifying i2c devices on Asus P8P67 sandybridge motherboard
Date: Wed, 26 Jan 2011 15:39:11 -0500 [thread overview]
Message-ID: <4D40866F.4080102@cfl.rr.com> (raw)
In-Reply-To: <4D4032CC.5010008-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
On 1/26/2011 9:42 AM, Phillip Susi wrote:
>> Back to your hardware monitoring issue, Asus tends to use the
>> integrated sensors in the Super-I/O on desktop boards. So odds are that
>> you have a very recent Super-I/O chip sensors-detect doesn't know. From
>> pictures found on the web, it seems to be a Nuvoton NCT6776F, for which
>> we indeed have no support yet.
>
> I began to suspect as much. Do you know if anyone is working on a
> driver for it, or if the data sheet is available so I could take a crack
> at it?
I have gotten ahold of the data sheet for the chip so hopefully will be
able to write a driver for it, but maybe we should move this
conversation to the lm-sensors mailing list?
Before we do though, I sill have one more question about the i2c bus.
My understanding is that simple i2c devices use fixed addresses, like
the SPD EEPROMs, but SMBus devices initially respond to a broadcast
address where they can be detected and dynamically assigned an address.
Is there a tool that can perform such a reset and enumeration that
could give better identification of those two unknown devices, should
they be smbus compatible and not just i2c? When I tried reading them
with i2c-dump I just got a bunch of XXs.
next prev parent reply other threads:[~2011-01-26 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 16:05 Identifying i2c devices on Asus P8P67 sandybridge motherboard Phillip Susi
[not found] ` <4D3EF4C0.1090008-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-01-25 16:42 ` Jean Delvare
[not found] ` <20110125174246.5061f881-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-01-25 23:52 ` Phillip Susi
[not found] ` <4D3F622B.9060003-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-01-26 8:22 ` Jean Delvare
[not found] ` <20110126092257.7b1243dd-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-01-26 14:42 ` Phillip Susi
[not found] ` <4D4032CC.5010008-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-01-26 20:39 ` Phillip Susi [this message]
[not found] ` <4D40866F.4080102-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-01-26 21:34 ` Jean Delvare
2011-01-26 21:37 ` 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=4D40866F.4080102@cfl.rr.com \
--to=psusi-3tlf1voikjtqt0dzr+alfa@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.