Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752892Ab1F0QzA (ORCPT <rfc822;w@1wt.eu>);
	Mon, 27 Jun 2011 12:55:00 -0400
Received: from mga02.intel.com ([134.134.136.20]:44372 "EHLO mga02.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752914Ab1F0Qy4 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 27 Jun 2011 12:54:56 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.65,433,1304319600"; 
   d="scan'208";a="20640189"
From: "R, Durgadoss" <durgadoss.r@intel.com>
To: "guenter.roeck@ericsson.com" <guenter.roeck@ericsson.com>
CC: Jean Delvare <khali@linux-fr.org>, "Yu, Fenghua" <fenghua.yu@intel.com>,
        "lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Alexander Stein <alexander.stein@systec-electronic.com>
Date: Mon, 27 Jun 2011 22:24:44 +0530
Subject: RE: [lm-sensors] coretemp: Support for Intel Atom E6XX CPU
 (TunnelCreek)?
Thread-Topic: [lm-sensors] coretemp: Support for Intel Atom E6XX CPU
 (TunnelCreek)?
Thread-Index: Acw06ljYrgjERCkkR0qmhcAeLOKPPgAADh2Q
Message-ID: <D6D887BA8C9DFF48B5233887EF04654109E84A62C7@bgsmsx502.gar.corp.intel.com>
References: <201106271220.51953.alexander.stein@systec-electronic.com>
	 <20110627164108.777c2e28@endymion.delvare>
	 <1309191054.8271.636.camel@groeck-laptop>
	 <D6D887BA8C9DFF48B5233887EF04654109E84A62C0@bgsmsx502.gar.corp.intel.com>
 <1309193405.8271.645.camel@groeck-laptop>
In-Reply-To: <1309193405.8271.645.camel@groeck-laptop>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id p5RGtPBg015010
Content-Length: 592
Lines: 17

Hi Guenter,

> Unfortunately, looking at Alexander's /proc/cpuinfo output, it looks
> like the E6xx chips have no mention of E6xx in the CPU ID string, which
> unfortunately kills the idea.
> 
> Do you know if there is _any_ means to distinguish E6xx from E6xxT ?
> 

Sorry I do not know. But I can ask some folks here and get back
to you guys. Should not take more time, once I identify the right
person to ask :-)

Thanks,
Durga

????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m????????????I?