public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gabriel C <crazy@frugalware.org>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
	Dan Williams <dan.j.williams@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] Status/support for Linux HECI from Intel? (for temp/voltage monitoring)
Date: Thu, 12 Feb 2009 02:35:27 +0100	[thread overview]
Message-ID: <49937CDF.10307@frugalware.org> (raw)
In-Reply-To: <1231356111.6648.2.camel@maxim-laptop>

Maxim Levitsky wrote:

> On Wed, 2009-01-07 at 11:42 -0500, Justin Piszcz wrote:
>> On Wed, 7 Jan 2009, Dan Williams wrote:
>>
>>> 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
>>>
>> Yeah that is the site-- however, will it ever get merged?  I have not 
>> heard anything about it for a year or so.
> 
> Nope, the heci is just a controller, but we need a way to tell that
> controller to show us the temperature data.
> But intel hasn't released the QST sdk, and probably never will.
> 
> Sad, 


Well I found this interesting thread about :

http://software.intel.com/en-us/forums/manageability-software-development/topic/54851/

It looks like the QST SDK already exists and is planned to be released..
(  http://software.intel.com/en-us/forums/manageability-software-development/topic/54851/reply/74068/ )

> 
> Best regards,
> 	Maxim Levitsky
> 

Gabriel


  reply	other threads:[~2009-02-12  1: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
2009-01-07 16:42   ` Justin Piszcz
2009-01-07 19:21     ` Maxim Levitsky
2009-02-12  1:35       ` Gabriel C [this message]
2009-02-12  2:36         ` [lm-sensors] " 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=49937CDF.10307@frugalware.org \
    --to=crazy@frugalware.org \
    --cc=dan.j.williams@intel.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=maximlevitsky@gmail.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