linux-kernel - Re: [PATCH 1/1] [hwmon] nct1008: Initial NCT1008 driver

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 6 Apr 2011 10:15:38 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Guenter Roeck <guenter.roeck@...csson.com>
Cc:	"achew@...dia.com" <achew@...dia.com>,
	"lm-sensors@...sensors.org" <lm-sensors@...sensors.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"w30289@...orola.com" <w30289@...orola.com>,
	"toddpoynor@...gle.com" <toddpoynor@...gle.com>,
	"wni@...dia.com" <wni@...dia.com>,
	"olofj@...omium.org" <olofj@...omium.org>
Subject: Re: [PATCH 1/1] [hwmon] nct1008: Initial NCT1008 driver

On Wed, 6 Apr 2011 00:32:22 -0700, Guenter Roeck wrote:
> Hi Jean,
> 
> On Wed, Apr 06, 2011 at 03:23:58AM -0400, Jean Delvare wrote:
> > Hi Andrew,
> > 
> [ ... ]
> > > +
> > > +/* Register Addresses */
> > > +#define LOCAL_TEMP_RD			0x00
> > > +#define EXT_HI_TEMP_RD			0x01
> > > +#define EXT_LO_TEMP_RD			0x10
> > > +#define STATUS_RD			0x02
> > > +#define CONFIG_RD			0x03
> > > +
> > > +#define CONFIG_WR			0x09
> > > +#define CONV_RATE_WR			0x0A
> > > +#define LOCAL_TEMP_HI_LIMIT_WR		0x0B
> > > +#define EXT_TEMP_HI_LIMIT_HI_BYTE	0x0D
> > > +#define OFFSET_WR			0x11
> > > +#define EXT_THERM_LIMIT_WR		0x19
> > > +#define LOCAL_THERM_LIMIT_WR		0x20
> > > +#define THERM_HYSTERESIS_WR		0x21
> > 
> > These register definitions look very familiar to me. Have you looked at
> > the lm90 driver to check has difficult it would be to add support for
> > the NCT1008? I bet it will only take a few lines of code.
> > 
> After I spent a couple of hours reviewing the driver, I noticed that the chip is functionally
> identical to ADT7461A (the only difference is the package; even the chip ID is the same),
> and the ADT7461A is in turn functionally identical to ADT7461. Sigh :(.

Yeah, this happens to me from times to times as well... I can't find of
a way to avoid such cases in the future unfortunately. Except that in
this specific case, the contributor should have noticed right away,
given that the compatibility if mentioned black on white in the
datasheet:

  "The NCT1008 is a dual−channel digital thermometer and
undertemperature/overtemperature alarm, intended for use in PCs and
thermal management systems. It is register−compatible with the
ADM1032 and ADT7461."

The good at least is that On Semi documented compatibility properly,
kudos to them.

-- 
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/