From: Jean Delvare <khali@linux-fr.org>
To: Yong Wang <yong.y.wang@linux.intel.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
Yuhong Bao <yuhongbao_386@hotmail.com>,
linux-kernel@vger.kernel.org, huaxu.wan@intel.com,
lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs
Date: Mon, 18 Jan 2010 09:14:51 +0100 [thread overview]
Message-ID: <20100118091451.7f103914@hyperion.delvare> (raw)
In-Reply-To: <20100118065821.GA19008@ywang-moblin2.bj.intel.com>
On Mon, 18 Jan 2010 14:58:21 +0800, Yong Wang wrote:
> On Sun, Jan 17, 2010 at 09:05:36PM +0100, Jean Delvare wrote:
> > That's where I am confused. The patch checks for the presence of the
> > Intel NM10, which, reading its description looks much like a south
> > bridge and not a memory controller (north bridge). So I think the patch
> > is wrong (or at least incomplete).
>
> Sorry, I made a mistake in the patch description. The new Atom CPU is
> coupled with integrated gfx and memory controller in one package. NM10
> chipset is another chip. This patch does check the presence of the
> integrated memory controller, i.e. 00:00.0 Host bridge device, which
> will always be present no matter whether NM10 chipset is used or not.
OK. Then indeed the patch description was rather bad. Even the comments
in the code are misleading, they mention the NM10 when they don't
really have to.
But at least if the code itself is OK... that's not that bad.
> > Anyway, how difficult would it be to set TjMax based on the CPUID? I
> > presume that the Intel Atom 400 and 500 series have their own CPUID
> > value, haven't they? This would seem even easier that checking for a
> > PCI device.
>
> CPUID value (family and model number) remains the same for all Atom CPUs
> thus far. That is why we check the new Atom CPU this way.
What about the stepping value? Don't these CPU models have their own?
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2010-01-18 8:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 7:31 [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Yong Wang
2010-01-06 15:08 ` Jean Delvare
2010-01-10 19:06 ` [lm-sensors] " Jean Delvare
2010-01-11 6:20 ` Yong Wang
2010-01-16 2:02 ` Yuhong Bao
2010-01-17 15:15 ` Jean Delvare
2010-01-17 19:29 ` Robert Hancock
2010-01-17 20:05 ` Jean Delvare
2010-01-18 6:58 ` Yong Wang
2010-01-18 8:14 ` Jean Delvare [this message]
2010-01-18 8:27 ` Yong Wang
2010-01-18 7:21 ` Huaxu Wan
2010-01-18 8:07 ` 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=20100118091451.7f103914@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=hancockrwd@gmail.com \
--cc=huaxu.wan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=yong.y.wang@linux.intel.com \
--cc=yuhongbao_386@hotmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox