From: Len Brown <lenb@kernel.org>
To: Carlos Corbacho <cathectic@slackadelic.com>
Cc: linux-acpi@vger.kernel.org, "Nashif, Anas" <anas.nashif@intel.com>
Subject: Re: [PATCH v4] ACPI: WMI: Add WMI-ACPI mapper driver
Date: Tue, 30 Oct 2007 14:18:22 -0400 [thread overview]
Message-ID: <200710301418.22639.lenb@kernel.org> (raw)
In-Reply-To: <200710300336.43696.cathectic@slackadelic.com>
When I consulted Anas about WMI, he recommended that Linux
expose WMI via CIMOM. I think that this means we'd need
to invent a sysfs interface for this acpi->wmi driver
to expose the hooks to a user-space daemon, which
would then make sense of it in Linux's management framework.
Anas provided the references below.
thanks,
-Len
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.
next prev parent reply other threads:[~2007-10-30 18:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 3:36 [PATCH v4] ACPI: WMI: Add WMI-ACPI mapper driver Carlos Corbacho
2007-10-30 13:47 ` Matthew Garrett
2007-10-30 14:28 ` Carlos Corbacho
2007-10-31 10:56 ` Carlos Corbacho
2007-10-30 18:18 ` Len Brown [this message]
2007-10-30 22:52 ` Carlos Corbacho
2007-10-31 0:18 ` Carlos Corbacho
2007-10-31 12:21 ` Carlos Corbacho
2007-10-31 16:24 ` Carlos Corbacho
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=200710301418.22639.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=anas.nashif@intel.com \
--cc=cathectic@slackadelic.com \
--cc=linux-acpi@vger.kernel.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