From: Andreas Herrmann <andreas.herrmann3@amd.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH 1/2] k8temp warn about errata
Date: Tue, 18 Nov 2008 11:26:12 +0000 [thread overview]
Message-ID: <20081118112612.GM12095@alberich.amd.com> (raw)
In-Reply-To: <48E3F505.40401@assembler.cz>
Hi Rudolf,
On Thu, Oct 02, 2008 at 12:09:09AM +0200, Rudolf Marek wrote:
> Index: linux-2.6.27-rc7/drivers/hwmon/k8temp.c
> =================================> --- linux-2.6.27-rc7.orig/drivers/hwmon/k8temp.c 2008-09-28 11:01:45.855284456 +0200
> +++ linux-2.6.27-rc7/drivers/hwmon/k8temp.c 2008-09-28 11:13:42.396117790 +0200
> @@ -155,6 +158,18 @@
> goto exit;
> }
>
> + /* get real PCI based cpuid, prior revF of fam 0Fh, this reg is 0 */
> + pci_read_config_dword(pdev, REG_CPUID, &cpuid);
I am just curious whether you have tested this on a CPU revision prior revF.
Because "BIOS and Kernel Developer's Guide for AMD Athlon 64 and AMD
Opteron Processors" suggests that this register exists for those older CPUs:
"CPUID Fn[8000_0001,0000_0001]_EAX Family, Model, Feature Identifiers
This register provides identical information to Function 3, Offset FCh."
(I don't have access to such a CPU model at the moment and thus can't
double-check this now.)
> +
> + data->fam = (cpuid & 0x00000f00) >> 8;
> + data->fam += (cpuid & 0x00f00000) >> 20;
> +
> + switch (data->fam) {
> + case 0xf:
> + dev_warn(&pdev->dev, "Temperature readouts might be wrong"
> + " - check errata #141\n");
> + }
> +
> pci_read_config_byte(pdev, REG_TEMP, &scfg);
> scfg &= ~(SEL_PLACE | SEL_CORE); /* Select sensor 0, core0 */
> pci_write_config_byte(pdev, REG_TEMP, scfg);
Regards,
Andreas
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2008-11-18 11:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 22:09 [lm-sensors] [PATCH 1/2] k8temp warn about errata Rudolf Marek
2008-10-25 12:43 ` Jean Delvare
2008-10-27 1:18 ` Jean-Marc Spaggiari
2008-11-09 19:56 ` Rudolf Marek
2008-11-09 20:47 ` Jean Delvare
2008-11-09 20:54 ` Jean Delvare
2008-11-10 1:27 ` Jordan Crouse
2008-11-10 9:38 ` Jean Delvare
2008-11-18 8:41 ` Andreas Herrmann
2008-11-18 8:55 ` Andreas Herrmann
2008-11-18 9:06 ` Jean Delvare
2008-11-18 9:25 ` Andreas Herrmann
2008-11-18 10:10 ` Andreas Herrmann
2008-11-18 10:40 ` Jean Delvare
2008-11-18 11:18 ` Andreas Herrmann
2008-11-18 11:26 ` Andreas Herrmann [this message]
2008-11-18 12:33 ` Jean Delvare
2008-11-18 12:57 ` Jean Delvare
2008-11-18 17:46 ` Jordan Crouse
2008-11-18 18:15 ` 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=20081118112612.GM12095@alberich.amd.com \
--to=andreas.herrmann3@amd.com \
--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.