All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Yuhong Bao <yuhongbao_386@hotmail.com>,
	yong.y.wang@linux.intel.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
Date: Sun, 17 Jan 2010 20:05:36 +0000	[thread overview]
Message-ID: <20100117210536.0ae0f187@hyperion.delvare> (raw)
In-Reply-To: <4B536502.20102@gmail.com>

On Sun, 17 Jan 2010 13:29:06 -0600, Robert Hancock wrote:
> On 01/17/2010 09:15 AM, Jean Delvare wrote:
> > On Fri, 15 Jan 2010 18:02:27 -0800, Yuhong Bao wrote:
> >>
> >>> No matter what chipset or gfx you use with the new Atom chip, the
> >>> integrated memory controller (IMC) will always be used. This patch
> >>> checks the presence of that IMC. Hope this clarifies.
> >> To be more precise, Pine Trail Atoms integrate the entire northbridge, including the integrated graphics and the memory controller into the CPU, and there is a DMI connection to the southbridge, which is the Intel NM10, that is NOT integrated.
> >
> > What prevents another vendor from selling a compatible south bridge
> > then?
> 
> Nothing (other than licensing for the DMI bus, see NVIDIA and the 
> problems this creates for their ION chipset). I'm assuming this patch is 
> checking for the host bridge device though, that is integrated into the 
> CPU and would always be present.

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).

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.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <khali@linux-fr.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Yuhong Bao <yuhongbao_386@hotmail.com>,
	yong.y.wang@linux.intel.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: Sun, 17 Jan 2010 21:05:36 +0100	[thread overview]
Message-ID: <20100117210536.0ae0f187@hyperion.delvare> (raw)
In-Reply-To: <4B536502.20102@gmail.com>

On Sun, 17 Jan 2010 13:29:06 -0600, Robert Hancock wrote:
> On 01/17/2010 09:15 AM, Jean Delvare wrote:
> > On Fri, 15 Jan 2010 18:02:27 -0800, Yuhong Bao wrote:
> >>
> >>> No matter what chipset or gfx you use with the new Atom chip, the
> >>> integrated memory controller (IMC) will always be used. This patch
> >>> checks the presence of that IMC. Hope this clarifies.
> >> To be more precise, Pine Trail Atoms integrate the entire northbridge, including the integrated graphics and the memory controller into the CPU, and there is a DMI connection to the southbridge, which is the Intel NM10, that is NOT integrated.
> >
> > What prevents another vendor from selling a compatible south bridge
> > then?
> 
> Nothing (other than licensing for the DMI bus, see NVIDIA and the 
> problems this creates for their ION chipset). I'm assuming this patch is 
> checking for the host bridge device though, that is integrated into the 
> CPU and would always be present.

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).

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.

-- 
Jean Delvare

  reply	other threads:[~2010-01-17 20:05 UTC|newest]

Thread overview: 25+ 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 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom Jean Delvare
2010-01-06 15:08   ` [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Jean Delvare
2010-01-10 19:06   ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom Jean Delvare
2010-01-10 19:06     ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Jean Delvare
2010-01-11  6:20     ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Yong Wang
2010-01-11  6:20       ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Yong Wang
2010-01-16  2:02       ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom Yuhong Bao
2010-01-16  2:02         ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Yuhong Bao
2010-01-17 15:15         ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom Jean Delvare
2010-01-17 15:15           ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Jean Delvare
2010-01-17 19:29           ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom Robert Hancock
2010-01-17 19:29             ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Robert Hancock
2010-01-17 20:05             ` Jean Delvare [this message]
2010-01-17 20:05               ` Jean Delvare
2010-01-18  6:58               ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Yong Wang
2010-01-18  6:58                 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Yong Wang
2010-01-18  8:14                 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom Jean Delvare
2010-01-18  8:14                   ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Jean Delvare
2010-01-18  8:27                   ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Yong Wang
2010-01-18  8:27                     ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Yong Wang
2010-01-18  7:21               ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom Huaxu Wan
2010-01-18  7:21                 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs Huaxu Wan
2010-01-18  8:07                 ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom Jean Delvare
2010-01-18  8:07                   ` [lm-sensors] [PATCH] hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs 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=20100117210536.0ae0f187@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 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.