From: Clemens Ladisch <clemens@ladisch.de>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Gigabyte MA785GMT-UD2H
Date: Tue, 08 Jun 2010 06:32:43 +0000 [thread overview]
Message-ID: <4C0DE40B.6030001@ladisch.de> (raw)
In-Reply-To: <E1OI4SR-000499-9R@mendel.bio.caltech.edu>
Jean Delvare wrote:
> On Mon, 07 Jun 2010 09:45:58 -0700, David Mathog wrote:
> > Product Name : Quadro FX 1400
> > PCI ID : ce10de
>
> 6-digit PCI IDs? Wow.
10de:00ce
> > I thought these CPUs had both per core sensors and a package sensor.
> > Why report only the last one? Maybe because some of Brisbane chips had
> > broken core sensors? This is Regor though, hopefully with working core
> > sensors.
The K10 CPUs have one internal temperature sensor which is shown
by k10temp, and one thermal diode that can be connected to the
motherboard's temperature sensor chip.
I see in the datasheet that revision D processors (six cores) can be
multi-node processors with two internal sensors, one for the entire CPU
and one for the second node. As far as I can tell, these would have two
northbridge PCI devices, and the k10temp driver would be attached to
both, resulting in two separate devices with temp1_value.
Regards,
Clemens
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2010-06-08 6:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 18:38 [lm-sensors] Gigabyte MA785GMT-UD2H David Mathog
2010-05-29 20:05 ` Jean Delvare
2010-06-01 18:22 ` David Mathog
2010-06-03 7:43 ` Jean Delvare
2010-06-03 17:56 ` David Mathog
2010-06-04 11:43 ` Jean Delvare
2010-06-04 17:23 ` David Mathog
2010-06-04 17:44 ` David Mathog
2010-06-05 11:53 ` Jean Delvare
2010-06-05 12:39 ` Jean Delvare
2010-06-07 16:45 ` David Mathog
2010-06-07 18:38 ` Jean Delvare
2010-06-08 6:32 ` Clemens Ladisch [this message]
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=4C0DE40B.6030001@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.