From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Phillip Susi <psusi-3tLf1voIkJTQT0dZR+AlfA@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 22:37:46 +0100 [thread overview]
Message-ID: <20110126223746.2d2141a1@endymion.delvare> (raw)
In-Reply-To: <4D4032CC.5010008-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
On Wed, 26 Jan 2011 09:42:20 -0500, Phillip Susi wrote:
> On 1/26/2011 3:22 AM, Jean Delvare 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?
No, the device isn't even listed on lm-sensors.org's wiki, I am not
aware of anyone working on it.
The datasheet isn't available for download from Nuvoton, but can
probably be requested from them.
> Then again, I wonder if it might be better to come up with an SSDT I can
> dynamically load to define the ACPI FAN and TZ objects and let the
> regular acpi driver manage it.
What an horrid idea. The ACPI FAN and TZ interfaces are very limited.
If the ACPI BIOS doesn't block access to the NCT6776F's I/O ports,
you'll be much better with a native driver.
OTOH I admit I am surprised to see Asus move away from the ATK0110.
--
Jean Delvare
prev parent reply other threads:[~2011-01-26 21:37 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
[not found] ` <4D40866F.4080102-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-01-26 21:34 ` Jean Delvare
2011-01-26 21:37 ` Jean Delvare [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=20110126223746.2d2141a1@endymion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=psusi-3tLf1voIkJTQT0dZR+AlfA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox