[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Wed, 12 Dec 2007 17:17:58 +0100
From: Andi Kleen <andi@...stfloor.org>
To: Mark Lord <lkml@....ca>
Cc: Anas Nashif <nashif@...ux.intel.com>,
Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Intel Management Engine Interface
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 using MEI driver.
> >
> >>>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).
> >>I would be more interested right now how the kernel can use this without
> >>additional user space support. Any ideas on this?
> >
> >I will dig for some documents on that.
> ..
>
> Sample code for storing a trace_back() would be much better.
Better just a patch that handles all oopses or perhaps better
all printk output (meconsole?)
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists