From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755450AbdEHTME (ORCPT ); Mon, 8 May 2017 15:12:04 -0400 Received: from esa2.dell-outbound.iphmx.com ([68.232.149.220]:21024 "EHLO esa2.dell-outbound.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754570AbdEHTMA (ORCPT ); Mon, 8 May 2017 15:12:00 -0400 From: X-LoopCount0: from 10.175.216.249 X-IronPort-AV: E=Sophos;i="5.38,310,1491282000"; d="scan'208";a="104157343" To: CC: , , , , , , , , , , Subject: RE: RFC: WMI Enhancements Thread-Topic: RFC: WMI Enhancements Thread-Index: AQHStXDRfWGz3Na/pUazu2XvXvLesqHF0EKAgASlkYCAABLTgIAA6aUAgAA5pYCAADDyAIAAOCOAgACXygCAADsZoIAAXFqA//+yhDCAAaJBgIAAfcEAgBdITWCAAHz2AP//vXJQgABepACABBB4gP//rG2wAASWK0QAAWGyMAAMKIoAAAp1Z9A= Date: Mon, 8 May 2017 19:11:57 +0000 Message-ID: <2aa696fd37b24c2ca18fc9f30b664ab1@ausx13mpc120.AMER.DELL.COM> References: <775ffd8f3327497cabd15ee7826cedaf@ausx13mpc120.AMER.DELL.COM> <20170505234436.GB25865@fury> <20170508152907.GA17700@fury> <20170508154725.GD17700@fury> <27661c9222e2452aa78ab1d1c1cd9015@ausx13mpc120.AMER.DELL.COM> <20170508190900.GF17700@fury> In-Reply-To: <20170508190900.GF17700@fury> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.208.86.26] Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id v48JC8K5029837 > -----Original Message----- > From: Darren Hart [mailto:dvhart@infradead.org] > Sent: Monday, May 8, 2017 2:09 PM > To: Limonciello, Mario > Cc: a.bokovoy@gmail.com; andy.shevchenko@gmail.com; luto@kernel.org; > pali.rohar@gmail.com; rjw@rjwysocki.net; len.brown@intel.com; > corentin.chary@gmail.com; andriy.shevchenko@linux.intel.com; linux- > kernel@vger.kernel.org; platform-driver-x86@vger.kernel.org; linux- > pm@vger.kernel.org > Subject: Re: RFC: WMI Enhancements > > On Mon, May 08, 2017 at 06:26:53PM +0000, Mario.Limonciello@dell.com wrote: > > (Responding as plain text, your email probably got punted from the ML from > being HTML) > > > > > > > > ... > > > > > > I'm not sure what you are asking about. Samba does not deal with WMI at all. > The state of affairs is > > > explained at https://powershell.org/2015/04/24/management-information- > the-omicimwmimidmtf-dictionary/ > > > -- old WMI (DCOM/RPC-based) is deprecated, new WMI based on WS-MAN is > supported and OMI is the > > > implementation. We used to have a very limited attemt at writing DCOM stack > and nobody worked on > > > it for years so it got removed. > > > > Thanks! That was a very interesting read. > > > > > Microsoft has already published a MOF parser as part of OMI work: > https://github.com/Microsoft/omi/ > > > under MIT license. > > > > Unfortunately that's expecting text MOF, not this intermediary compiled format. > > > > I presume which of these to use is the decision of the vendor? No, MS documentation indicates to store binary MOF in the ACPI buffer. >Is there a > transition going on from BMOF to Text MOF? Or will both be part of products for > the near term? > Binary MOF will be part of products unless MS or a standards group decides to announce something new for OEM's to use in this space. > I'm trying to understand if BMOF is a legacy thing now, or if it will continue > to be used in new designs. Should be continued to use in new designs.