[lkml]   [2007]   [Dec]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] Intel Management Engine Interface
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 as a
proxy for SOAP messages coming for management applications. LMS is available via

The demo we had for storing kernel oops messages in the firmware used the AMT
1.0 interface (legacy) which allowed direct access to 3PDS using the MEI driver
interfaces. In AMT 3.0 (current platforms) this has been disabled and only SOAP
is possible which 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).


Andi Kleen wrote:
> Anas Nashif <> writes:
>> The Intel Management Engine Interface (aka HECI: Host Embedded
>> Controller Interface ) enables communication between the host OS and
>> the Management Engine firmware. MEI is bi-directional, and either the
>> host or Intel AMT firmware can initiate transactions.
> Can you please expand a bit on who on the host OS would actually communicate
> with the management engine? It looks like this driver just exports
> an interface to user space. What user space would use it and for
> what?
> I would be definitely interested in a way to save oops information
> away using this. I remember you had a demo for this, is support
> for that coming soon?
> -Andi
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to
> More majordomo info at
> Please read the FAQ at

 \ /
  Last update: 2007-12-11 19:41    [W:0.045 / U:5.188 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site