From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Analogue Devices ADT7476ARQZ chip status
Date: Sat, 26 Nov 2005 12:58:48 +0000 [thread overview]
Message-ID: <20051126125944.6044c55e.khali@linux-fr.org> (raw)
In-Reply-To: <4387E587.20302@reub.net>
Hi Reuben,
> > Please provide a dump of the Analog Devices chip:
> > i2cdump 0 0x2e b
>
> [root@typhoon ~]# i2cdump 0 0x2e b
> (...)
> 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
> 00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 20: 77 6c c3 c5 be 36 29 27 62 0c 57 0d 46 36 ff ff wl???6)'b?W?F6..
> 30: 33 4c 4c 00 00 00 00 00 ff ff ff 00 00 76 41 69 3LL..........vAi
This matches what the ADT7476 datasheet says. I've added support in
sensors-detect (in CVS). Please test if possible.
I've also added an entry in our "New Drivers" page.
My first impression is that the ADT7476 is partly compatible with the
ADT7467/ADT7468, which is itself partly compatible with the ADT7463,
which is an improved version of the ADM1027, which is itself mostly
compatible with the National Semiconductor LM85. We have a driver
(lm85) which covers the LM85, ADM1027 and ADT7463. If we want to
support the ADT7467/ADT7468 and ADT7476, I think we should start a new
driver. The lm85 driver already supports many chips, let's not add to
the mess.
--
Jean Delvare
next prev parent reply other threads:[~2005-11-26 12:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 5:33 [lm-sensors] Analogue Devices ADT7476ARQZ chip status Reuben Farrelly
2005-11-26 10:51 ` Jean Delvare
2005-11-26 10:57 ` Reuben Farrelly
2005-11-26 11:56 ` Henrique de Moraes Holschuh
2005-11-26 12:13 ` Jean Delvare
2005-11-26 12:58 ` Jean Delvare [this message]
2005-11-26 13:31 ` Henrique de Moraes Holschuh
2005-11-26 14:11 ` Reuben Farrelly
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=20051126125944.6044c55e.khali@linux-fr.org \
--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.