public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Oren Weil <oren.jer.weil@intel.com>
Cc: gregkh@suse.de, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, alan@linux.intel.com,
	david@woodhou.se
Subject: Re: [PATCH 8/8] staging/mei: Updates to staging/Kconfig ane staging/Makefile and a new Makefile and Kconfig
Date: Wed, 27 Apr 2011 20:05:50 -0400	[thread overview]
Message-ID: <10935.1303949150@localhost> (raw)
In-Reply-To: Your message of "Wed, 27 Apr 2011 13:27:37 +0300." <1303900057-21694-9-git-send-email-oren.jer.weil@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

On Wed, 27 Apr 2011 13:27:37 +0300, Oren Weil said:
> Changes of Kconfig and Makefile in drivers/staging
> for adding the Intel MEI Driver to the Linux kernel.
> New Makefile and Kconfig building for MEI Driver.

> +++ b/drivers/staging/mei/Kconfig
> @@ -0,0 +1,10 @@
> +config INTEL_MEI
> +	tristate "Intel Management Engine Interface (Intel MEI)"
> +	depends on X86 && EXPERIMENTAL
> +	help
> +		The Intel Management Engine (Intel ME) provides Manageability,
> +		Security and Media services for system containing Intel chipsets.
> +		if selected /dev/mei misc device will be created.
> +
> +		For more information see
> +		<http://software.intel.com/en-us/manageability/>

Can this be expanded a bit to give a better hint *which* Intel chipsets support
this? I just spent an honest 10 minutes looking around that website, and am no
clearer on whether the 82801I in my laptop supports this.  Having a line like
"server chipsets XY948 and later and ICH10 and later" or similar would be a big
help to all those who hit this when it goes into the tree.


[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2011-04-28  0:06 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 10:27 [PATCH 0/8] staging/mei: Intel MEI Driver Oren Weil
2011-04-27 10:27 ` [PATCH 1/8] staging/mei: PCI device and char driver support Oren Weil
2011-04-27 12:24   ` Jiri Slaby
2011-04-27 15:05   ` Greg KH
2011-04-28  5:47     ` Weil, Oren jer
2011-04-28 13:37       ` Greg KH
2011-04-27 10:27 ` [PATCH 2/8] staging/mei: Interrupt handling Oren Weil
2011-04-27 10:27 ` [PATCH 3/8] staging/mei: MEI "Link" layer code - MEI Hardware communications Oren Weil
2011-04-27 15:18   ` Greg KH
2011-04-27 10:27 ` [PATCH 4/8] staging/mei: MEI driver init flow Oren Weil
2011-04-27 10:27 ` [PATCH 5/8] staging/mei: Hardware and MEI driver internal struct definition Oren Weil
2011-04-27 10:27 ` [PATCH 6/8] staging/mei: Header file contain the Userland API, (IOCTL and its struct) Oren Weil
2011-04-27 15:02   ` Greg KH
2011-04-27 15:15   ` Randy Dunlap
2011-04-27 15:33     ` Greg KH
2011-04-28  6:29       ` Weil, Oren jer
2011-04-28 13:40         ` Greg KH
2011-04-28 14:12           ` Weil, Oren jer
2011-04-28 15:04             ` Greg KH
2011-04-28 15:39               ` David Woodhouse
2011-04-28 14:43           ` Alan Cox
2011-04-27 10:27 ` [PATCH 7/8] staging/mei: AMT Watchdog Oren Weil
2011-04-27 13:53   ` Arnd Bergmann
2011-04-27 15:07     ` Greg KH
2011-04-28  5:51       ` Weil, Oren jer
2011-04-28 12:50         ` Arnd Bergmann
2011-04-28 13:38         ` Greg KH
2011-04-27 10:27 ` [PATCH 8/8] staging/mei: Updates to staging/Kconfig ane staging/Makefile and a new Makefile and Kconfig Oren Weil
2011-04-27 15:06   ` Greg KH
2011-04-28  6:39     ` Weil, Oren jer
2011-04-28  8:22       ` Alan Cox
2011-04-27 15:19   ` Randy Dunlap
2011-04-28  0:05   ` Valdis.Kletnieks [this message]
2011-04-27 15:03 ` [PATCH 0/8] staging/mei: Intel MEI Driver Greg KH

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=10935.1303949150@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=alan@linux.intel.com \
    --cc=david@woodhou.se \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oren.jer.weil@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