From: Robert Hancock <hancockrwd@gmail.com>
To: Jean Delvare <khali@linux-fr.org>
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 13:29:06 -0600 [thread overview]
Message-ID: <4B536502.20102@gmail.com> (raw)
In-Reply-To: <20100117161518.4912be7c@hyperion.delvare>
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.
>
> I start believing that we'd rather identify these Atom models using
> CPUID rather than a PCI device.
>
next prev parent reply other threads:[~2010-01-17 19:29 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 [this message]
2010-01-17 20:05 ` Jean Delvare
2010-01-18 6:58 ` Yong Wang
2010-01-18 8:14 ` Jean Delvare
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=4B536502.20102@gmail.com \
--to=hancockrwd@gmail.com \
--cc=huaxu.wan@intel.com \
--cc=khali@linux-fr.org \
--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