On Wed, Dec 12, 2007 at 10:00:24AM -0500, Mark Lord wrote:
> Anas Nashif wrote:
> >
> >Actually no TCP/IP is needed here. Basically the MEI driver writes and
> >reads the
> >messages to/from the firmware. When communicating in-band using LMS, TCP/IP
> >terminates at LMS and the messages are copied
Anas Nashif wrote:
Actually no TCP/IP is needed here. Basically the MEI driver writes and reads the
messages to/from the firmware. When communicating in-band using LMS, TCP/IP
terminates at LMS and the messages are copied using MEI driver.
To have a feel for all of this, with many examples, sa
Anas Nashif wrote:
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.
There is a little
> Actually no TCP/IP is needed here. Basically the MEI driver writes and reads
> the
> messages to/from the firmware. When communicating in-band using LMS, TCP/IP
> terminates at LMS and the messages are copied using MEI driver.
Ah that's good to know. I suspect the SOAP interchange could be stri
On Tue, Dec 11, 2007 at 11:02:02AM -0800, David Miller wrote:
> From: Andi Kleen <[EMAIL PROTECTED]>
> Date: Tue, 11 Dec 2007 19:53:17 +0100
>
> > Ok but saving oops is such a useful facility that we'll probably
> > need to think about implementing SOAP in the kernel.
>
> Ummm, no.
>
> UDP is st
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 as
From: Andi Kleen <[EMAIL PROTECTED]>
Date: Tue, 11 Dec 2007 19:53:17 +0100
> Ok but saving oops is such a useful facility that we'll probably
> need to think about implementing SOAP in the kernel.
Ummm, no.
UDP is stateless, a stripped down copy of TCP we simply
do not need. We also do not need
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 as a
> proxy for SOAP messages c
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
http://openam
Anas Nashif <[EMAIL PROTECTED]> 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 tran
10 matches
Mail list logo
