From: Jean Delvare <khali@linux-fr.org>
To: 宾西蒙 <binximeng@gmail.com>
Cc: Guenter Roeck <guenter.roeck@ericsson.com>,
Jim Cromie <jim.cromie@gmail.com>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ethan Lawrence <e.law87@yahoo.com>,
lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org,
lars4910@hotmail.com, birdie@permonline.ru, jadcock@cox.net
Subject: Re: [lm-sensors] [PATCH/RFC v2] hwmon: Add support for W83667HG-B
Date: Sat, 03 Jul 2010 20:56:13 +0000 [thread overview]
Message-ID: <20100703225613.1236bf07@hyperion.delvare> (raw)
In-Reply-To: <1278152148.7319.11.camel@xli51>
Hi 宾西蒙,
On Sat, 03 Jul 2010 12:15:48 +0200, 宾西蒙 wrote:
> 在 2010-07-03六的 10:35 +0200，Jean Delvare写道：
> > Hi Guenter,
> >
> > On Fri, 2 Jul 2010 02:23:26 -0700, Guenter Roeck wrote:
> > > + w83667hg-i 9 5 3 3 0xb340 0xc1 0x5ca3
> >
> > As discussed before, this one is a 677 series, not 667. That being
> > said, I admit that the device ID proximity between the 667HG-B and the
> > 677HG-I is troubling, and invites to optimism as far as compatibility
> > between these two chips is concerned.
>
> I think we got something confused here, I was looking for the W836
> *seven* 7 HG-I driver (which has ID 0xb470) and not the W836 *six* 7
> HG-I one, although maybe someone else might benefit from that one.
Yes, there was some confusion. For one thing, the W83667HG-I does not
exist. And for another, I have no idea where Guenter found the device
id 0xb340. None of the Nuvoton W836x7HG datasheets I have mention this
ID. All I know of is 0xb350 for the W83667HG-B and 0xb470 for the
W83677HG-I (which apparently was renamed to something different
meanwhile.)
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <khali@linux-fr.org>
To: 宾西蒙 <binximeng@gmail.com>
Cc: Guenter Roeck <guenter.roeck@ericsson.com>,
Jim Cromie <jim.cromie@gmail.com>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ethan Lawrence <e.law87@yahoo.com>,
lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org,
lars4910@hotmail.com, birdie@permonline.ru, jadcock@cox.net
Subject: Re: [PATCH/RFC v2] hwmon: Add support for W83667HG-B and W83667HG-I to w83627ehf driver.
Date: Sat, 3 Jul 2010 22:56:13 +0200 [thread overview]
Message-ID: <20100703225613.1236bf07@hyperion.delvare> (raw)
In-Reply-To: <1278152148.7319.11.camel@xli51>
Hi 宾西蒙,
On Sat, 03 Jul 2010 12:15:48 +0200, 宾西蒙 wrote:
> 在 2010-07-03六的 10:35 +0200，Jean Delvare写道：
> > Hi Guenter,
> >
> > On Fri, 2 Jul 2010 02:23:26 -0700, Guenter Roeck wrote:
> > > + w83667hg-i 9 5 3 3 0xb340 0xc1 0x5ca3
> >
> > As discussed before, this one is a 677 series, not 667. That being
> > said, I admit that the device ID proximity between the 667HG-B and the
> > 677HG-I is troubling, and invites to optimism as far as compatibility
> > between these two chips is concerned.
>
> I think we got something confused here, I was looking for the W836
> *seven* 7 HG-I driver (which has ID 0xb470) and not the W836 *six* 7
> HG-I one, although maybe someone else might benefit from that one.
Yes, there was some confusion. For one thing, the W83667HG-I does not
exist. And for another, I have no idea where Guenter found the device
id 0xb340. None of the Nuvoton W836x7HG datasheets I have mention this
ID. All I know of is 0xb350 for the W83667HG-B and 0xb470 for the
W83677HG-I (which apparently was renamed to something different
meanwhile.)
--
Jean Delvare
next prev parent reply other threads:[~2010-07-03 20:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 9:23 [lm-sensors] [PATCH/RFC v2] hwmon: Add support for W83667HG-B and Guenter Roeck
2010-07-02 9:23 ` [PATCH/RFC v2] hwmon: Add support for W83667HG-B and W83667HG-I to w83627ehf driver Guenter Roeck
2010-07-03 8:35 ` [lm-sensors] [PATCH/RFC v2] hwmon: Add support for W83667HG-B Jean Delvare
2010-07-03 8:35 ` [PATCH/RFC v2] hwmon: Add support for W83667HG-B and W83667HG-I to w83627ehf driver Jean Delvare
2010-07-03 10:15 ` [lm-sensors] [PATCH/RFC v2] hwmon: Add support for W83667HG-B 宾西蒙
2010-07-03 10:15 ` [PATCH/RFC v2] hwmon: Add support for W83667HG-B and W83667HG-I to w83627ehf driver 宾西蒙
2010-07-03 20:56 ` Jean Delvare [this message]
2010-07-03 20:56 ` Jean Delvare
2010-07-03 21:28 ` [lm-sensors] [PATCH/RFC v2] hwmon: Add support for W83667HG-B Guenter Roeck
2010-07-03 21:28 ` [PATCH/RFC v2] hwmon: Add support for W83667HG-B and W83667HG-I to w83627ehf driver Guenter Roeck
2010-07-03 15:11 ` [lm-sensors] [PATCH/RFC v2] hwmon: Add support for W83667HG-B Guenter Roeck
2010-07-03 15:11 ` [PATCH/RFC v2] hwmon: Add support for W83667HG-B and W83667HG-I to w83627ehf driver Guenter Roeck
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=20100703225613.1236bf07@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=akpm@linux-foundation.org \
--cc=binximeng@gmail.com \
--cc=birdie@permonline.ru \
--cc=e.law87@yahoo.com \
--cc=guenter.roeck@ericsson.com \
--cc=hsweeten@visionengravers.com \
--cc=jadcock@cox.net \
--cc=jim.cromie@gmail.com \
--cc=lars4910@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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.