public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Anas Nashif <anas.nashif@intel.com>
To: Len Brown <lenb@kernel.org>
Cc: Carlos Corbacho <carlos@strangeworlds.co.uk>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	linux-acpi@vger.kernel.org
Subject: Re: Exposing WMI on Linux
Date: Mon, 11 Feb 2008 10:42:48 -0500	[thread overview]
Message-ID: <47B06CF8.5020404@intel.com> (raw)
In-Reply-To: <200802062336.17586.lenb@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

      reply	other threads:[~2008-02-11 15:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7905FFCA2E893B41B7697977B01334D4029723ED@hdsmsx411.amr.corp.intel.com>
2008-02-07  4:36 ` Exposing WMI on Linux Len Brown
2008-02-11 15:42   ` Anas Nashif [this message]

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=47B06CF8.5020404@intel.com \
    --to=anas.nashif@intel.com \
    --cc=carlos@strangeworlds.co.uk \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    /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