From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anas Nashif Subject: Re: Exposing WMI on Linux Date: Mon, 11 Feb 2008 10:42:48 -0500 Message-ID: <47B06CF8.5020404@intel.com> References: <7905FFCA2E893B41B7697977B01334D4029723ED@hdsmsx411.amr.corp.intel.com> <200802062336.17586.lenb@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mga02.intel.com ([134.134.136.20]:45637 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753863AbYBKPog (ORCPT ); Mon, 11 Feb 2008 10:44:36 -0500 In-Reply-To: <200802062336.17586.lenb@kernel.org> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Len Brown Cc: Carlos Corbacho , Matthew Garrett , linux-acpi@vger.kernel.org Len, Ok, I will take a deep dive into this and try to provide answers to the questions below, including how to use the data in management frameworks such as CIMOMs. Anas Len Brown wrote: > On Wednesday 30 May 2007 16:12, you wrote: >> Here are some pointers as promised: >> >> http://developer.novell.com/wiki/index.php/OMC >> >> This is a Novell project with many providers dealing will many aspects >> of the OS. They also provide RPMs for OpenSUSE and is the main source >> for the OpenWBEM CIMOM binaries for SUSE. >> >> http://sblim.wiki.sourceforge.net/ >> >> Is the IBM project dealing with instrumentation and home of the SFCB >> CIMOM targeting embedded environments and only supports CMPI providers. >> >> http://sblim.wiki.sourceforge.net/ProviderCmpiSysfs is a sysfs provider. >> Seems to be old but is a good example. >> >> http://openpegasus.org/ >> >> This is the home of the OpenPeagsus CIMOM, supported by multiple >> vendors. >> >> http://www.dmtf.org/standards/wbem/ is about the WBEM protocol. Also the >> tutorial is good: http://www.wbemsolutions.com/tutorials/CIM/wbem.html >> >> http://cimple.org/ tries to make writing providers easy. >> > > Anas, > We could use some help on how to expose WMI to user-space in Linux. > (Then we could use some help on user-space using that interface:-) > > Carlos has cooked up an ACPI-WMI mapping driver for Linux, > and has two in-kernel platform specific drivers that want > to talk to it (acer-laptop and HP Compaq TC1100 Tablets), > and Matthew has been poking at an HP driver to use WMI > to access some laptop functionas as well. > > But nobody is thinking about how to hook this up > to the user-space management infrastructure in Linux, > and what the kernel/user interface to to best do > that would be. > > Carlos prototyped a sysfs I/F, but that doesn't seem to fit > the WMI transaction model, so he's wondering if an ioctl > I/F would be more appropriate where transaction consistency > can be enforced by the driver, perhaps with a library > on top of it. > > Please advise. > > thanks, > -Len