From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Asus P5B Deluxe WiFi AP Sensors
Date: Wed, 06 Sep 2006 18:38:07 +0000 [thread overview]
Message-ID: <20060906203807.dad64215.khali@linux-fr.org> (raw)
In-Reply-To: <20060822145643.GA5632@seahunt.dyndns.org>
Hi David,
> The "No such device" error is probably here in the source code:
> dev_err(dev, "unknown CHIP_ID (0x%02x)\n", i);
> err = -ENODEV;
> goto exit_remove;
>
> This error occurs if the chip is not recognized in w83627ehf_detect():
>
> /* Detect w83627ehf (10 VIN) and w83627dhg (9 VIN) */
> i = w83627ehf_read_value(client, W83627EHF_REG_CHIP_ID);
> if (i = 0xa1) { /* w83627ehf */
> dev_dbg(dev, "detected W83627EHF/EHG (A1)\n");
> data->num_in = 10;
> }
> else if (i = 0xc1) { /* w83627dhg */
> dev_dbg(dev, "detected W83627DHG (C1)\n");
> data->num_in = 9;
> }
> else {
> dev_err(dev, "unknown CHIP_ID (0x%02x)\n", i);
> err = -ENODEV;
> goto exit_remove;
> }
No, actually the error occurs before that. You didn't add the Super-I/O
ID of the W83627DHG in w83627ehf_find, so that function will return
-ENODEV.
--
Jean Delvare
next prev parent reply other threads:[~2006-09-06 18:38 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 14:56 [lm-sensors] Asus P5B Deluxe WiFi AP Sensors Michael Nelson
2006-08-22 20:27 ` Rudolf Marek
2006-08-22 21:38 ` Michael Nelson
2006-08-23 1:09 ` Michael Nelson
2006-08-23 15:01 ` Jean Delvare
2006-08-23 16:25 ` Michael Nelson
2006-08-26 13:25 ` Michael Nelson
2006-08-26 21:21 ` Jean Delvare
2006-08-26 22:22 ` Michael Nelson
2006-09-01 13:12 ` Michael Nelson
2006-09-02 5:54 ` Jean Delvare
2006-09-02 6:24 ` David Hubbard
2006-09-02 11:04 ` Jean Delvare
2006-09-02 12:54 ` Michael Nelson
2006-09-02 16:04 ` David Hubbard
2006-09-05 9:10 ` Jean Delvare
2006-09-05 9:17 ` Yuan Mu
2006-09-05 15:05 ` David Hubbard
2006-09-05 15:09 ` Michael Nelson
2006-09-06 5:31 ` David Hubbard
2006-09-06 5:33 ` David Hubbard
2006-09-06 12:15 ` Michael Nelson
2006-09-06 13:43 ` Michael Nelson
2006-09-06 14:03 ` Jean Delvare
2006-09-06 14:07 ` Michael Nelson
2006-09-06 14:26 ` Michael Nelson
2006-09-06 14:40 ` Jean Delvare
2006-09-06 15:07 ` Michael Nelson
2006-09-06 15:28 ` Michael Nelson
2006-09-06 18:08 ` David Hubbard
2006-09-06 18:19 ` Michael Nelson
2006-09-06 18:38 ` Jean Delvare [this message]
2006-09-06 18:59 ` Jean Delvare
2006-09-06 21:42 ` David Hubbard
2006-09-06 23:02 ` Michael Walle
2006-09-07 1:37 ` Michael Nelson
2006-09-07 6:20 ` David Hubbard
2006-09-07 7:46 ` Jean Delvare
2006-09-07 7:59 ` Jean Delvare
2006-09-07 13:23 ` Michael Nelson
2006-09-07 19:34 ` Rudolf Marek
2006-09-07 21:12 ` Michael Walle
2006-09-08 1:12 ` Michael Nelson
2006-09-08 1:43 ` Michael Nelson
2006-09-10 17:52 ` Jean Delvare
2006-09-10 19:46 ` Michael Nelson
2006-09-10 20:13 ` Michael Nelson
2006-09-20 16:16 ` Jean Delvare
2006-09-21 18:22 ` David Hubbard
2006-09-22 13:51 ` Michael Nelson
2006-12-10 23:30 ` David Hubbard
2006-12-11 4:09 ` David Hubbard
2006-12-11 17:41 ` David Holl
2006-12-11 18:59 ` David Hubbard
2006-12-11 22:10 ` David Holl
2006-12-11 22:16 ` David Hubbard
2006-12-15 3:34 ` David Hubbard
2006-12-15 5:05 ` David Holl
2006-12-15 5:14 ` Con Kolivas
2006-12-15 5:48 ` David Hubbard
2006-12-16 5:48 ` David Holl
2006-12-17 9:50 ` Jean Delvare
2006-12-17 9:55 ` Jean Delvare
2006-12-17 9:59 ` 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=20060906203807.dad64215.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.