To: Anas Nashif <nashif@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Intel Management Engine Interface
From: Andi Kleen <andi@firstfloor.org>
References: <475EC9C1.9080708@linux.intel.com>
Date: Tue, 11 Dec 2007 19:14:31 +0100
In-Reply-To: <475EC9C1.9080708@linux.intel.com> (Anas Nashif's message of "Tue\, 11 Dec 2007 12\:32\:49 -0500")
Message-ID: <p7363z5nlo8.fsf@bingen.suse.de>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 937
Lines: 22

Anas Nashif <nashif@linux.intel.com> 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 majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/