From: Clemens Ladisch <clemens@ladisch.de>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Support for Family 10h CPUs - Not all sensors are
Date: Mon, 23 Nov 2009 07:58:37 +0000 [thread overview]
Message-ID: <4B0A40AD.2040702@ladisch.de> (raw)
In-Reply-To: <232a75d96e552164f4c7073154b36172.squirrel@unimail.uni-dortmund.de>
Jean Delvare wrote:
> On Sat, 21 Nov 2009 18:28:25 +0100, Jan Bessai wrote:
> > according to AMD (
> > http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/41322.pdf
> > ) not all AMD K10 CPUs have defect sensors. In fact only DR-* revisions
> > are affected. All CPUs with Socket AM3 as well as all Phenom II Processors
> > and some Opterons are unaffected (DA-*, RB-*, HY-*).
> > Please reconsider the statement "Embedded sensors are known to be
> > unreliable, and won't be supported ever.".
>
> We can do that. But how does this translate into CPUID numbers?
Family 0xF, extended family 1, model 2.
Or, to quote a certain driver that happend to be posted on this list
recently:
static bool __devinit has_erratum_319(void)
{
/*
* Erratum 319: The thermal sensor of older Family 10h processors
* (B steppings) may be unreliable.
*/
return boot_cpu_data.x86 = 0x10 && boot_cpu_data.x86_model <= 2;
}
HTH
Clemens
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-11-23 7:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 17:28 [lm-sensors] Support for Family 10h CPUs - Not all sensors are Jan Bessai
2009-11-21 20:11 ` Jean Delvare
2009-11-22 20:18 ` Jan Bessai
2009-11-23 7:58 ` Clemens Ladisch [this message]
2009-11-23 9:28 ` Jean Delvare
2009-11-23 11:27 ` Clemens Ladisch
2009-11-23 12:22 ` 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=4B0A40AD.2040702@ladisch.de \
--to=clemens@ladisch.de \
--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.