mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Gabriel C <nix.or.die@googlemail.com>
Cc: Gabriel C <crazy@frugalware.org>,
	Maxim Levitsky <maximlevitsky@gmail.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>,
	Andriy Gapon <avg@icyb.net.ua>
Subject: Re: [lm-sensors] Status/support for Linux HECI from Intel? (for  temp/voltage monitoring)
Date: Mon, 4 Jan 2010 08:54:03 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1001040851490.29475@p34.internal.lan> (raw)
In-Reply-To: <1820d69d1001040551k26cfd925q4ada6b226740ac30@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 3604 bytes --]



On Mon, 4 Jan 2010, Gabriel C wrote:

> 2009/2/12 Justin Piszcz <jpiszcz@lucidpixels.com>:
>>
>>
>> On Thu, 12 Feb 2009, Gabriel C wrote:
>>
>>> 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/
>>> )
>> I volunteer to test any patches if/when they are created after the SDK is
>> released.
>>
>
>
> Again me .. Well the SDK is *still* not released ..  The Intel folks
> said back in August :
>
> "The latest word is that the SDK is being prepared for approval but it
> is contingent upon an upcoming platform release."
>
> ( whatever that means )
>
>
> Anyway Andriy Gapon has posted on lm-sensors some nice tool to read
> the sensors output ( thx :) )
> (http://lists.lm-sensors.org/pipermail/lm-sensors/2009-October/026830.html)
>
> Today I'm out from hospital so I've decided to quick hack this tool
> and make it work on Linux.
>
> Here the output from my DQ45CB mobo:
>
> crazy@thor:~/INTEL/QST/Li$ sudo ./heci-qst
> CPU  Temp:      56.00   °C
> MB   Temp:      31.14   °C
> ICH  Temp:      67.37   °C
> MCH  Temp:      66.00   °C
> CPU  Fan:       1080    RPM
> INL  Fan:       1202    RPM
> OUTL Fan:       288     RPM
> +12  Volts:     11.965  V
> +5   Volts:     5.021   V
> +3.3 Volts:     3.316   V
> MCH  Vccp:      1.122   V
> CPU1 Vccp:      1.125   V
>
> Justin I know is not based on released SDK of Intel but maybe you
> still want to do some tests ?:)
Hi,

I upgraded my system and have a new board now, I do have another system that
uses the same board (DG965WH) if you have a patch/URL with the software I
can give it a run.

Justin.

>
> ( of course you need the heci kernel modules first )
>
> @Andriy there is a smallish bug in your original code .. you should
> use ..... , abs(value) ...., abs(value) ...);
> that will solve the negative CPU TEMP values you get with your version.
>
> Best Regards,
>
> Gabriel C
>

  reply	other threads:[~2010-01-04 13:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30 12:26 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       ` [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 [this message]
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=alpine.DEB.2.00.1001040851490.29475@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=avg@icyb.net.ua \
    --cc=crazy@frugalware.org \
    --cc=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=maximlevitsky@gmail.com \
    --cc=nix.or.die@googlemail.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

all inboxes | Powered by JetHome®