The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Alexander Stein <alexander.stein@systec-electronic.com>
To: "R, Durgadoss" <durgadoss.r@intel.com>
Cc: "guenter.roeck@ericsson.com" <guenter.roeck@ericsson.com>,
	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>
Subject: Re: [lm-sensors] coretemp: Support for Intel Atom E6XX CPU (TunnelCreek)?
Date: Wed, 3 Aug 2011 14:58:00 +0200	[thread overview]
Message-ID: <201108031458.01805.alexander.stein@systec-electronic.com> (raw)
In-Reply-To: <D6D887BA8C9DFF48B5233887EF04654109E84A62C7@bgsmsx502.gar.corp.intel.com>

Hello,

On Monday 27 June 2011 18:54:44 R, Durgadoss wrote:
> > 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 :-)

Any news on this topic?

Regards,
Alexander

  reply	other threads:[~2011-08-03 12:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 10:20 coretemp: Support for Intel Atom E6XX CPU (TunnelCreek)? Alexander Stein
2011-06-27 13:42 ` Guenter Roeck
2011-06-27 14:41 ` Jean Delvare
2011-06-27 16:05   ` Alexander Stein
2011-06-27 16:10   ` Guenter Roeck
2011-06-27 16:40     ` [lm-sensors] " R, Durgadoss
2011-06-27 16:50       ` Guenter Roeck
2011-06-27 16:54         ` R, Durgadoss
2011-08-03 12:58           ` Alexander Stein [this message]
2011-08-03 13:26             ` R, Durgadoss
2011-08-03 14:40               ` Alexander Stein
2011-09-16 16:21                 ` 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=201108031458.01805.alexander.stein@systec-electronic.com \
    --to=alexander.stein@systec-electronic.com \
    --cc=durgadoss.r@intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=guenter.roeck@ericsson.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox