Messages in this thread | | | Date | Tue, 22 Mar 2011 09:23:05 -0700 | From | Greg KH <> | Subject | Re: [PATCH 0/7] char/mei: Intel MEI Driver |
| |
On Tue, Mar 22, 2011 at 12:51:25PM +0200, Oren Weil wrote: > Intel MEI Driver > ======================= > The Intel Management Engine (Intel ME) is an isolated and > protected computing resources (Coprocessor) residing inside > Intel chipsets. The Intel ME provides support for computer/IT > management features. > The Feature set depends on Intel chipset SKU. > > The Intel Management Engine Interface (Intel MEI, previous known > as HECI) is interface between the Host and Intel ME. > This interface is exposed to the host as PCI device. > The Intel MEI Driver is in charge of the communication channel > between host application and ME feature. > > Each ME feature (ME Client) is addressed by GUID/UUID > and each feature defines its own protocol. > The protocol is message based with header and payload up to > 512 bytes. > > The driver exposes character device called /dev/mei.
Why not use a misc device node instead of claiming your own major number? That would solve your sysfs code solution for you as well (enabling you to delete it all.)
> drivers/char/mei/Makefile | 19 +
How about putting it under drivers/misc/mei/ instead? That's where other monitoring drivers like this are at (ibmasm for example.)
Are you wanting this version reviewed for inclusion in .40? If you don't feel the code is ready for the main kernel tree, do you want it in staging for the .40 release?
thanks,
greg k-h -- 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/
| |