Re: [PATCH] Intel Management Engine Interface

2007-12-11 Thread Anas Nashif
is why in the demo we changed the ME firmware to use AMT 1.0. To have a feel for all of this, with many examples, samples and documentation you can download the AMT 3.0 SDK (google: intel amt sdk). Anas Andi Kleen wrote: Anas Nashif [EMAIL PROTECTED] writes: The Intel Management Engine Interface

Re: [PATCH] Intel Management Engine Interface

2007-12-11 Thread Anas Nashif
Andi Kleen wrote: On Tue, Dec 11, 2007 at 01:38:10PM -0500, Anas Nashif wrote: There are different ways you can connect to the Firmware and it all depends on the ME subsystem you want to communicate with. For Intel AMT, you would use LMS (Local Manageability Service) which acts

[PATCH] Intel Manageability Engine Interface driver

2007-10-22 Thread Anas Nashif
The Manageability Engine Interface (aka HECI) allows applications to communicate with the Intel(R) Manageability Engine (ME) firmware. It is meant to be used by user-space manageability applications to access ME features such as Intel(R) Active Management Technology, Intel(R) Quiet System

Re: [PATCH] Intel Manageability Engine Interface driver

2007-10-23 Thread Anas Nashif
Andrew, Thanks for the feedback. Andrew Morton wrote: On Mon, 22 Oct 2007 13:22:38 -0400 Anas Nashif [EMAIL PROTECTED] wrote: The patch is large so I'm placing the diff on the web for download rather than attaching it here. Download: http://download.openamt.org/intel-MEI.diff Please get

Re: [PATCH] Intel Manageability Engine Interface driver

2007-10-23 Thread Anas Nashif
Hi, Maxim Levitsky wrote: Will integrated sensors on DG965 motherboard be supported? They can be accessed only through the HECI interface, but the board has no AMT, and even if it had one, I don't think AMT includes HW sensors. True, this is supported using QST. Will it be supported?

[PATCH] Intel Manageability Engine Interface driver

2007-10-22 Thread Anas Nashif
The Manageability Engine Interface (aka HECI) allows applications to communicate with the Intel(R) Manageability Engine (ME) firmware. It is meant to be used by user-space manageability applications to access ME features such as Intel(R) Active Management Technology, Intel(R) Quiet System

Re: [PATCH] Intel Manageability Engine Interface driver

2007-10-23 Thread Anas Nashif
Andrew, Thanks for the feedback. Andrew Morton wrote: On Mon, 22 Oct 2007 13:22:38 -0400 Anas Nashif <[EMAIL PROTECTED]> wrote: The patch is large so I'm placing the diff on the web for download rather than attaching it here. Download: http://download.openamt.org/intel-MEI.diff

Re: [PATCH] Intel Manageability Engine Interface driver

2007-10-23 Thread Anas Nashif
Hi, Maxim Levitsky wrote: Will integrated sensors on DG965 motherboard be supported? They can be accessed only through the HECI interface, but the board has no AMT, and even if it had one, I don't think AMT includes HW sensors. True, this is supported using QST. Will it be supported?

Re: [PATCH] Intel Management Engine Interface

2007-12-11 Thread Anas Nashif
is why in the demo we changed the ME firmware to use AMT 1.0. To have a feel for all of this, with many examples, samples and documentation you can download the AMT 3.0 SDK (google: intel amt sdk). Anas Andi Kleen wrote: > Anas Nashif <[EMAIL PROTECTED]> writes: >> The Intel Ma

Re: [PATCH] Intel Management Engine Interface

2007-12-11 Thread Anas Nashif
Andi Kleen wrote: > On Tue, Dec 11, 2007 at 01:38:10PM -0500, Anas Nashif wrote: >> There are different ways you can connect to the Firmware and it all depends >> on >> the ME subsystem you want to communicate with. >> For Intel AMT, you would use LMS (Local Manage