public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Anas Nashif <nashif@linux.intel.com>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Intel Management Engine Interface
Date: Wed, 12 Dec 2007 10:00:24 -0500	[thread overview]
Message-ID: <475FF788.5000906@rtr.ca> (raw)
In-Reply-To: <475EDFA3.1070001@linux.intel.com>

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.

-ml

  parent reply	other threads:[~2007-12-12 15:00 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 17:32 [PATCH] Intel Management Engine Interface Anas Nashif
2007-12-11 18:14 ` Andi Kleen
2007-12-11 18:38   ` Anas Nashif
2007-12-11 18:53     ` Andi Kleen
2007-12-11 19:02       ` David Miller
2007-12-11 19:47         ` Andi Kleen
2007-12-11 19:06       ` Anas Nashif
2007-12-11 19:48         ` Andi Kleen
2007-12-12 15:00         ` Mark Lord [this message]
2007-12-12 16:17           ` Andi Kleen
2007-12-12  8:48 ` Alexander E. Patrakov
  -- strict thread matches above, loose matches on Subject: below --
2008-05-20  0:11 Anas Nashif
2008-05-20  0:28 ` Andrew Morton
2008-05-20 19:02   ` Gabriel C
2008-05-22 16:51   ` Pavel Machek
2008-05-20 15:42 ` Maxim Levitsky
2008-05-20 20:35 ` Carlos R. Mafra
2008-05-20 22:27 ` Jiri Slaby
2008-05-23  7:04 ` Pavel Machek
2008-07-17 18:27 Marcin Obara
2008-07-18  0:00 ` Randy Dunlap
2008-07-18  5:44 ` Marcin Obara
2008-07-18 17:39   ` Marcin Obara
2008-07-18 19:23     ` Marcin Obara
2008-07-18 20:30       ` Marcin Obara
2008-07-23 18:00         ` Marcin Obara
2008-08-11 19:23           ` Marcin Obara
2008-08-12  4:53             ` Andrew Morton
2008-08-12 16:15               ` Jiri Slaby
2008-08-12 19:24                 ` Marcin Obara
2008-08-12 19:24                   ` Alan Cox
2008-08-12 21:03                   ` Arjan van de Ven
2008-08-13  0:58             ` Greg KH
2008-08-13  7:16               ` Marcin Obara
2008-08-13 18:18                 ` Greg KH
2008-08-13 19:48                   ` Marcin Obara
2008-08-14  0:23                     ` Greg KH
2008-07-18  9:27 ` Andi Kleen
2008-07-18 10:51   ` Marcin Obara
2008-07-18 11:02     ` Andi Kleen
2008-07-18 11:33       ` Marcin Obara
2008-08-06 16:56 ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=475FF788.5000906@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nashif@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox