Date: Sun, 9 May 2010 10:54:35 +0900 From: Norikatsu Shigemura <nork@FreeBSD.org> To: Jung-uk Kim <jkim@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: amdtemp(4) issue Message-ID: <20100509105435.766b9629.nork@FreeBSD.org> In-Reply-To: <201005051351.15012.jkim@FreeBSD.org> References: <20100505154312.49e7a2cc.nork@FreeBSD.org> <201005051351.15012.jkim@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi jkim. On Wed, 5 May 2010 13:51:10 -0400 Jung-uk Kim <jkim@FreeBSD.org> wrote: > > 11 - 0x01 = +10C > > 11 - 0x18 = -13C > > 11 - 0x3f = -52C > > [*] http://support.amd.com/us/Processor_TechDocs/31116.pdf > AMD keeps flipping the sign from core to core. :-( Please see > AMDTEMP_FLAG_DO_SIGN for Family 0Fh, for example. In fact, Linux > driver (k10temp) does not care about the DiodeOffset at all. > Instead, they just say "input" temperature. Oh my god... OK, I see. > > I got following thermal related registers in amdtemp_gettemp > > function: May 5 15:06:53 nadesico kernel: amdtemp0: F3x64 Hardware > > Thermal Control(HTC) Register = 0x3a4c0005 May 5 15:06:53 nadesico > > kernel: amdtemp0: F3x68 Software Thermal Control(STC) Register = > > 0x10000000 May 5 15:06:53 nadesico kernel: amdtemp0: F3xA4 > > Reported Temperature Control Register = 0x000c1880 May 5 15:06:53 > > nadesico kernel: amdtemp0: F3xE4 Thermtrip Status Register > > = 0x1cc01830 May 5 15:06:53 nadesico kernel: amdtemp0: F3xE8 > > Northbridge Capabilities Register = 0x0207df19 > > But I don't have any idea to fix register's paraemters. Do you > > have any idea? > Sorry, I don't. You may find Linux k10temp driver > (drivers/hwmon/k10temp.c) useful, though. Thank you, I'll compare other implementations.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100509105435.766b9629.nork>