From: Dan Williams <dan.j.williams@intel.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>
Subject: Re: Status/support for Linux HECI from Intel? (for temp/voltage monitoring)
Date: Wed, 07 Jan 2009 09:41:34 -0700 [thread overview]
Message-ID: <4964DB3E.6080908@intel.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0812300700410.11356@p34.internal.lan>
Justin Piszcz wrote:
> The HECI interface would allow lm_sensors developers to grab the
> temperatures off the chips on the board.
>
> From 2005(?)-2008 there was some chatter about supporting it but it never
> seemed to happen, is there any eventual planned support for supporting
> Intel's HECI interface or if the user wants to see the
> temperatures/voltages just buy a different motherboard with an ITE I/O
> controller?
>
> I have a couple DG965WH boards and it would be nice to see the
> temperature of the chipset etc without having to reboot into the BIOS.
>
Hi Justin,
I am not up to date on the progress in this area, but perhaps this site
(http://www.openamt.org/) has what you are looking for?
Regards,
Dan
next prev parent reply other threads:[~2009-01-07 16:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 12:26 Status/support for Linux HECI from Intel? (for temp/voltage monitoring) Justin Piszcz
2009-01-07 16:41 ` Dan Williams [this message]
2009-01-07 16:42 ` Justin Piszcz
2009-01-07 19:21 ` Maxim Levitsky
2009-02-12 1:35 ` [lm-sensors] " Gabriel C
2009-02-12 2:36 ` Joshua D Doll
2009-02-12 17:39 ` Justin Piszcz
2010-01-04 13:51 ` Gabriel C
2010-01-04 13:54 ` Justin Piszcz
2010-01-04 14:09 ` Gabriel C
2010-01-04 14:22 ` Justin Piszcz
2010-01-04 14:43 ` Gabriel C
2010-01-04 14:55 ` Justin Piszcz
2010-01-04 15:07 ` Gabriel C
2010-01-13 8:19 ` Andriy Gapon
2010-02-23 17:56 ` Gabriel C
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=4964DB3E.6080908@intel.com \
--to=dan.j.williams@intel.com \
--cc=jpiszcz@lucidpixels.com \
--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