lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 3 Jul 2010 09:39:43 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Guenter Roeck <guenter.roeck@...csson.com>
Cc:	Jim Cromie <jim.cromie@...il.com>,
	H Hartley Sweeten <hsweeten@...ionengravers.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ethan Lawrence <e.law87@...oo.com>,
	"lm-sensors@...sensors.org" <lm-sensors@...sensors.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"lars4910@...mail.com" <lars4910@...mail.com>,
	"birdie@...monline.ru" <birdie@...monline.ru>,
	"jadcock@....net" <jadcock@....net>
Subject: Re: [PATCH/RFC] hwmon: Add support for W83667HG-B

On Fri, 2 Jul 2010 09:15:21 -0700, Guenter Roeck wrote:
> On Fri, Jul 02, 2010 at 10:59:03AM -0400, Jean Delvare wrote:
> > On Fri, 2 Jul 2010 07:09:44 -0700, Guenter Roeck wrote:
> > > On Fri, Jul 02, 2010 at 05:51:23AM -0400, Jean Delvare wrote:
> > > > FYI, I have a datasheet, which unfortunately I am not allowed to share.
> > > > Please let me know if you want me to look up something for you.
> > > > 
> > > How about the changed registers ? Would give us an idea if the chip is closer to 
> > > 667 or to 667-B.
> > 
> > There is no summary of this available. The only way is to go through
> > both datasheets and compare all registers in sequence. This takes time,
> > which is exactly why I couldn't find the time to do it :(
> > 
> Yes, I noticed. Changes can be quite subtle, too. 
> 
> I'll remove the HG-I chip detection from the next patch rev
> unless I manage to get a datasheet as well.

I agree. The 667HG-B support seems to be easier to get, and more urgent
too, judging by the number of requests. Let's get this tested and
upstream first, and then we see what can be done for the 677HG-I.

-- 
Jean Delvare
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ