From: Guenter Roeck <guenter.roeck@ericsson.com>
To: "R, Durgadoss" <durgadoss.r@intel.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>
Subject: RE: [lm-sensors] coretemp: Support for Intel Atom E6XX CPU (TunnelCreek)?
Date: Mon, 27 Jun 2011 09:50:05 -0700 [thread overview]
Message-ID: <1309193405.8271.645.camel@groeck-laptop> (raw)
In-Reply-To: <D6D887BA8C9DFF48B5233887EF04654109E84A62C0@bgsmsx502.gar.corp.intel.com>
On Mon, 2011-06-27 at 12:40 -0400, R, Durgadoss wrote:
> Hi Guenter,
>
> > I thought about replacing the manual TjMax detection code with code
> > using the model string to take care of problems like this - essentially
> > by providing a table with entries { model string, Tjmax } for each CPU
> > with Tjmax other than 100 degrees C. This way we could get rid of some
> > of the odd code we have today. Would that make sense ?
>
> I completely agree with you here.
> This way, a lot of code in get_tjmax will be reduced, by just
> a search through some array.
>
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 ?
Thanks,
Guenter
next prev parent reply other threads:[~2011-06-27 16:50 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 [this message]
2011-06-27 16:54 ` R, Durgadoss
2011-08-03 12:58 ` Alexander Stein
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=1309193405.8271.645.camel@groeck-laptop \
--to=guenter.roeck@ericsson.com \
--cc=alexander.stein@systec-electronic.com \
--cc=durgadoss.r@intel.com \
--cc=fenghua.yu@intel.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