[lm-sensors] Intel(r) Quiet System Technology (QST) SDK Is Now

[lm-sensors] Intel(r) Quiet System Technology (QST) SDK Is Now

[Pearson, Scott]

[-- Attachment #2: Type: text/plain, Size: 564 bytes --]

In case you hadn't seen the notice, the open source release of the Intel(r) Quiet System Technology (QST) SDK is now available. Go to http://software.intel.com/en-us/articles/Intel_Quiet_System_Technology_Software_Development_Kit/ to download both the SDK and the Programmer's Reference Manual (PRM)...

N. Scott Pearson
S/W Architect, Intel Channel Boards Division (iCBD)
PC Client Group (PCCG), Intel Architecture Group (IAG)
Desk  503-696-7818   Cell    503-702-6412
Fax   503-696-1015   E-Mail  scott.pearson@intel.com<mailto:scott.pearson@intel.com>


[-- Attachment #3: Type: text/html, Size: 6194 bytes --]

Re: [lm-sensors] Intel(r) Quiet System Technology (QST) SDK Is Now

[Mark M. Hoffman]

Hi Scott:

* Pearson, Scott <scott.pearson@intel.com> [2010-03-08 15:23:18 -0700]:
>    In case you hadn't seen the notice, the open source release of the Intel�
>    Quiet System Technology (QST) SDK is now available. Go to
>    [1]http://software.intel.com/en-us/articles/Intel_Quiet_System_Technology_Software_Development_Kit/
>    to download both the SDK and the Programmer's Reference Manual (PRM)...

It was pointed out by an lm-sensors user earlier, yes; but thank you.

http://software.intel.com/en-us/articles/intel-quiet-system-technology-intel-qst-sdk-software-license/

I'm not a lawyer, but at a quick glance this does not look GPL compatible.
Thus, this release is of very little value to the developers on this list.

A dual license, with the second license being GPLv2 (or even BSD) would be
the most obvious way to address this problem.  I hope Intel will consider
modifying the license of this SDK so that lm-sensors devs can use it.

Thanks & regards,

-- 
Mark M. Hoffman
mhoffman@lightlink.com


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel(r) Quiet System Technology (QST) SDK Is Now

[Pearson, Scott]

The Intel® QST SDK is licensed under BSD 2.0. It looks like the license agreement that they put on the web page is the wrong one (I just contacted them and they are going to correct this). Download the SDK package and look at the license that is actually in the README file; it should be more to your liking...

N. Scott Pearson
S/W Architect, Intel Channel Boards Division (iCBD)
PC Client Group (PCCG), Intel Architecture Group (IAG)
Desk  503-696-7818   Cell    503-702-6412
Fax   503-696-1015   E-Mail  scott.pearson@intel.com


-----Original Message-----
From: Mark M. Hoffman [mailto:mhoffman@lightlink.com] 
Sent: Monday, March 08, 2010 6:06 PM
To: Pearson, Scott
Cc: lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] Intel(r) Quiet System Technology (QST) SDK Is Now Available...

Hi Scott:

* Pearson, Scott <scott.pearson@intel.com> [2010-03-08 15:23:18 -0700]:
>    In case you hadn't seen the notice, the open source release of the Intel�
>    Quiet System Technology (QST) SDK is now available. Go to
>    [1]http://software.intel.com/en-us/articles/Intel_Quiet_System_Technology_Software_Development_Kit/
>    to download both the SDK and the Programmer's Reference Manual (PRM)...

It was pointed out by an lm-sensors user earlier, yes; but thank you.

http://software.intel.com/en-us/articles/intel-quiet-system-technology-intel-qst-sdk-software-license/

I'm not a lawyer, but at a quick glance this does not look GPL compatible.
Thus, this release is of very little value to the developers on this list.

A dual license, with the second license being GPLv2 (or even BSD) would be
the most obvious way to address this problem.  I hope Intel will consider
modifying the license of this SDK so that lm-sensors devs can use it.

Thanks & regards,

-- 
Mark M. Hoffman
mhoffman@lightlink.com

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel(r) Quiet System Technology (QST) SDK Is Now

[Mark M. Hoffman]

Hi Scott:

* Pearson, Scott <scott.pearson@intel.com> [2010-03-09 11:03:31 -0700]:
> The Intel® QST SDK is licensed under BSD 2.0. It looks like the license
> agreement that they put on the web page is the wrong one (I just contacted
> them and they are going to correct this). Download the SDK package and look
> at the license that is actually in the README file; it should be more to your
> liking...

That's great news!  Thanks for your reply.

Regards,

-- 
Mark M. Hoffman
mhoffman@lightlink.com


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel(r) Quiet System Technology (QST) SDK Is Now

[Pearson, Scott]

No problem. At the same time, I also wanted to make you are aware of some other changes that occurred in conjunction with this SDK release...

In many desktop motherboards that utilize the just-released 5 Series chipset, version 2.0 of the Intel(R) Quiet System Technology (QST) firmware is included. Within this firmware, we significantly revamped the command packet protocol that is used for communicating with and querying Intel(R) QST. Any support that you may have implemented for the Intel(R) 965, Intel(R) 3 Series and/or Intel(R) 4 Series chipsets will not work with the new firmware. Within the SDK, we have included a compatibility layer that will allow software that is written to use the new 2.0 command protocol to also support the older chipsets and firmware versions. Since we have provided the full source for this compatibility layer in the SDK (the SDK actually contains no binaries; everything is in source form), you should be able to move to the new protocol - and still retain support for the legacy chipsets - quite easily...

Let me know what questions you have...

N. Scott Pearson
S/W Architect, Intel Channel Boards Division (iCBD)
PC Client Group (PCCG), Intel Architecture Group (IAG)
Desk  503-696-7818   Cell    503-702-6412
Fax   503-696-1015   E-Mail  scott.pearson@intel.com


-----Original Message-----
From: Mark M. Hoffman [mailto:mhoffman@lightlink.com] 
Sent: Tuesday, March 09, 2010 10:29 AM
To: Pearson, Scott
Cc: lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] Intel(r) Quiet System Technology (QST) SDK Is Now Available...

Hi Scott:

* Pearson, Scott <scott.pearson@intel.com> [2010-03-09 11:03:31 -0700]:
> The Intel(r) QST SDK is licensed under BSD 2.0. It looks like the license
> agreement that they put on the web page is the wrong one (I just contacted
> them and they are going to correct this). Download the SDK package and look
> at the license that is actually in the README file; it should be more to your
> liking...

That's great news!  Thanks for your reply.

Regards,

-- 
Mark M. Hoffman
mhoffman@lightlink.com


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel(r) Quiet System Technology (QST) SDK Is Now

[Gabriel C]

On 09.03.2010 19:56, Pearson, Scott wrote:

> No problem. At the same time, I also wanted to make you are aware of some other changes that occurred in conjunction with this SDK release...
> 
> In many desktop motherboards that utilize the just-released 5 Series chipset, version 2.0 of the Intel(R) Quiet System Technology (QST) firmware

> is included. Within this firmware, we significantly revamped the command packet protocol that is used for communicating with and querying Intel(R) QST. 

> Any support that you may have implemented for the Intel(R) 965, Intel(R) 3 Series and/or Intel(R) 4 Series chipsets will not work with the new firmware. 

> Within the SDK, we have included a compatibility layer that will allow software that is written to use the new 2.0 command protocol to also support the 
> older chipsets and firmware versions. Since we have provided the full source for this compatibility layer in the SDK (the SDK actually contains no binaries; 
> everything is in source form), you should be able to move to the new protocol - and still retain support for the legacy chipsets - quite easily...

> 
> Let me know what questions you have...
> 


Hi Scott,

I think in first place we need an HECI driver for Linux ?:)

There isn't any 'officially' HECI support for Linux at all. Last release from openamt is back in 2008 and broken 
( and even patched up to work somewhat it does not support AMT 6.0 probably not even all of AMT 5 features ).. 

Last commit to openamts source tree is 17 months back and it seems any development on this stopped.(?)

Also 'heci' was in the staging tree of the kernel for a short time but since no-one from Intel cared it was removed.
See : http://lkml.org/lkml/2009/9/3/3

What is the status of the HECI driver(s) for Linux please ? I mean this situation is somewhat weird.. Now the SDK is there but the HECI driver(s) .. heh
 

> N. Scott Pearson
> S/W Architect, Intel Channel Boards Division (iCBD)
> PC Client Group (PCCG), Intel Architecture Group (IAG)
> Desk  503-696-7818   Cell    503-702-6412
> Fax   503-696-1015   E-Mail  scott.pearson@intel.com

Best Regards,

Gabriel C

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel(r) Quiet System Technology (QST) SDK Is Now

[Pearson, Scott]

Gabriel,

I was on the periphery for the driver effort and certainly not privy to any of the discussions that took place regarding commitments and support, so I cannot respond well to your query. A fact of life is that we do not have enough people to do everything and we must make - sometimes painful - decisions regarding what we can and cannot commit to doing/supporting. This is one of those places where resources were put in place for a period of time but, following that, had to be committed to other tasks...

What I can tell you is that the Intel(r) Management Engine Interface (MEI) is a hardware interface that supports communications between software entities executing on the main processor and firmware entities executing on the Intel(r) Management Engine. The MEI (HECI) driver facilitates the use of this hardware interface - and that's all it does. As such, it is agnostic to the "features" of firmware entities such as Intel(r) AMT or Intel(r) QST. Upper layer software would, of course, need to understand the features and communications protocols of the particular firmware subsystems that they are communicating with but, strictly from the standpoint of the driver, the only difference from one chipset generation to another is the PCI id(s) for the MEI in the different flavor(s) of the newer generation chipset. Thus, in theory, to support (for example) the Series 5 chipset, all you should need to do is add support for the appropriate ids and you are done. If you look in the driver source at file heci.h, you will see a list of definitions for the ids that are supported. In file heci_main.c, you will see these definitions used to form a search list. Simply expand the definitions and list to include the id(s) for the missing generation(s) and you should be good to go. The ids can typically be found in the particular chipset's Specification Update document...

N. Scott Pearson
S/W Architect, Intel Channel Boards Division (iCBD)
PC Client Group (PCCG), Intel Architecture Group (IAG)
Desk  503-696-7818   Cell    503-702-6412
Fax   503-696-1015   E-Mail  scott.pearson@intel.com


-----Original Message-----
From: Gabriel C [mailto:nix.or.die@googlemail.com] 
Sent: Wednesday, March 10, 2010 8:24 AM
To: Pearson, Scott
Cc: Mark M. Hoffman; lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] Intel(r) Quiet System Technology (QST) SDK Is Now Available...

Hi Scott,

I think in first place we need an HECI driver for Linux ?:)

There isn't any 'officially' HECI support for Linux at all. Last release from openamt is back in 2008 and broken 
( and even patched up to work somewhat it does not support AMT 6.0 probably not even all of AMT 5 features ).. 

Last commit to openamts source tree is 17 months back and it seems any development on this stopped.(?)

Also 'heci' was in the staging tree of the kernel for a short time but since no-one from Intel cared it was removed.
See : http://lkml.org/lkml/2009/9/3/3

What is the status of the HECI driver(s) for Linux please ? I mean this situation is somewhat weird.. Now the SDK is there but the HECI driver(s) .. heh
 

> N. Scott Pearson
> S/W Architect, Intel Channel Boards Division (iCBD)
> PC Client Group (PCCG), Intel Architecture Group (IAG)
> Desk  503-696-7818   Cell    503-702-6412
> Fax   503-696-1015   E-Mail  scott.pearson@intel.com

Best Regards,

Gabriel C

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel(r) Quiet System Technology (QST) SDK Is Now

[Valentijn Scholten]

I believe we're another step further now that Intel has releasedtheir new AMT 
drivers:

http://software.intel.com/en-us/forums/showthread.php?t‚888

http://software.intel.com/en-us/articles/download-the-latest-intel-amt-open-
source-drivers/




_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Intel(r) Quiet System Technology (QST) SDK Is Now

[Valentijn Scholten]

Pearson, Scott <scott.pearson <at> intel.com> writes:

>  eration chipset. Thus, in theory, to support (for example) the Series 5 
chipset, all you should need to do is
> add support for the appropriate ids and you are done. If you look in the 
driver source at file heci.h, you
> will see a list of definitions for the ids that are supported. In file 
heci_main.c, you will see these
> definitions used to form a search list. Simply expand the definitions and list 
to include the id(s) for the
> missing generation(s) and you should be good to go. The ids can typically be 
found in the particular
> chipset's Specification Update document...
I found an interesting post on the intel forums containing some intel patch info 
the get the heci driver working with the newer chipsets.

I just compiled the heci driver and can confirm it works with Intel QST SDK on a 
DH55TC motherboard. Running Debian Squeeze = kernel 2.6.32.
On 2.6.36+kernels the driver doesn't compile due to some ioctl changes.

Output:


Intel(R) Quiet System Technology Status Display Demo
Copyright (C) 2007-2008, Intel Corporation. All Rights Reserved.

The QST Subsystem is configured and operational

Current Lock Mask:

   Configuration:        Locked
   Health Thresholds:    Unlocked
   Manual Fan Control:   Unlocked
   SST Bus Resources:    Read-Only
   Chipset Resources:    Read-Only

Sensor Configuration/Status Summary:

   Temperature Sensor 1:

      Health:            Normal
      Usage:             Processor Temperature
      Reading:           30.60

      NonCrit:           95.000
      Crit:              97.000
      NonRecov:          99.000

   Temperature Sensor 3:

      Health:            Normal
      Usage:             Peripheral Controller Hub (PCH) Temperature
      Reading:           59.00

      NonCrit:           110.000
      Crit:              114.000
      NonRecov:          117.000

   Temperature Sensor 4:

      Health:            Normal
      Usage:             Voltage Regulator Temperature
      Reading:           43.00

      NonCrit:           113.000
      Crit:              117.000
      NonRecov:          121.000


   Temperature Sensor 5:

      Health:            Normal
      Usage:             Memory DIMM Temperature
      Reading:           34.00

      NonCrit:           113.000
      Crit:              117.000
      NonRecov:          121.000

   Fan Speed Sensor 1:

      Health:            Normal
      Usage:             Processor Fan
      Reading:           644

      NonCrit:           300.000
      Crit:              250.000
      NonRecov:          200.000

   Voltage Sensor 1:

      Health:            Normal
      Usage:             +12 Volts
      Reading:           12.172

      NonCrit Low:       11.400
      Crit Low:          11.100
      NonRecov Low:      10.800

      NonCrit High:      12.600
      Crit High:         12.900
      NonRecov High:     13.200

   Voltage Sensor 2:


      Health:            Normal
      Usage:             +5 Volts
      Reading:           4.937

      NonCrit Low:       4.750
      Crit Low:          4.625
      NonRecov Low:      4.500

      NonCrit High:      5.250
      Crit High:         5.375
      NonRecov High:     5.500

   Voltage Sensor 3:

      Health:            Normal
      Usage:             +3.3 Volts
      Reading:           3.286

      NonCrit Low:       3.135
      Crit Low:          3.053
      NonRecov Low:      2.970

      NonCrit High:      3.465
      Crit High:         3.548
      NonRecov High:     3.630

   Voltage Sensor 4:

      Health:            Normal
      Usage:             +1.5 Volts
      Reading:           1.533

      NonCrit Low:       1.425
      Crit Low:          1.415
      NonRecov Low:      1.400

      NonCrit High:      1.575
      Crit High:         1.585
      NonRecov High:     1.600


   Voltage Sensor 5:

      Health:            Normal
      Usage:             Processor Vcc
      Reading:           0.932

      NonCrit Low:       0.463
      Crit Low:          0.363
      NonRecov Low:      0.263

      NonCrit High:      1.863
      Crit High:         1.963
      NonRecov High:     2.063

Fan Speed Controller Configuration/Status Summary:

   Fan Speed Controller 1:

      Health:            Normal
      Usage:             Processor Fan Controller
      Control:           Automatic
      Duty Cycle:        20.00

   Fan Speed Controller 2:

      Health:            Normal
      Usage:             Chassis Inlet Fan Controller
      Control:           Automatic
      Duty Cycle:        30.00

   Fan Speed Controller 3:

      Health:            Normal
      Usage:             Chassis Outlet Fan Controller
      Control:           Automatic
      Duty Cycle:        30.00

Good news.


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors