From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Anas Nashif <nashif@linux.intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Intel Management Engine Interface
Date: Thu, 22 May 2008 18:51:57 +0200 [thread overview]
Message-ID: <20080522165156.GA7431@ucw.cz> (raw)
In-Reply-To: <20080519172821.023fb28f.akpm@linux-foundation.org>
Hi!
> > We have addressed more issues raised on lkml after initial submission,
> > especially the legacy device support issue which was removed in this
> > patch.
> >
> > 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.
> >
> > The core hardware architecture of Intel Active Management Technology
> > (Intel AMT) is resident in firmware. The micro-controller within the
> > chipset's graphics and memory controller (GMCH) hub houses the
> > Management Engine (ME) firmware, which implements various services
> > on behalf of management applications.
> >
> > Some of the ME subsystems that can be access via MEI driver:
> >
> > - Intel(R) Quiet System Technology (QST) is implemented as a firmware
> > subsystem that runs in the ME. Programs that wish to expose the
> > health monitoring and fan speed control capabilities of Intel(R) QST
> > will need to use the MEI driver to communicate with the ME sub-system.
> > - ASF is the "Alert Standard Format" which is an DMTF manageability
> > standard. It is implemented in the PC's hardware and firmware, and is
> > managed from a remote console.
> >
> > Most recent Intel desktop chipsets have one or more of the above ME
> > services. The MEI driver will make it possible to support the above
> > features on Linux and provides applications access to the ME and it's
> > features.
>
> What a lot of code.
>
> It'd be nice if the changelog were to describe the proposed and
> all-important kernel<->userspace interface, please. From a five-second
> peek it looks like a miscdev with ioctls? Ah, and there's read and
> write too.
Actuallly, we already have perfectly good interface for sensor-like
stuff -- in lm_sensors. Even acpi is moving in that direction...
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-05-23 7:10 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 0:11 [PATCH] Intel Management Engine Interface Anas Nashif
2008-05-20 0:28 ` Andrew Morton
2008-05-20 19:02 ` Gabriel C
2008-05-22 16:51 ` Pavel Machek [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
2007-12-11 17:32 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
2007-12-12 16:17 ` Andi Kleen
2007-12-12 8:48 ` Alexander E. Patrakov
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=20080522165156.GA7431@ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.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