On Thu, Apr 13, 2017 at 08:44:28AM -0700, Andy Lutomirski wrote: > On Thu, Apr 13, 2017 at 8:39 AM, Pali Rohár <pali.rohar@xxxxxxxxx> wrote: > > On Thursday 13 April 2017 17:32:48 Andy Lutomirski wrote: > >> On Thu, Apr 13, 2017 at 12:32 AM, Michał Kępień <kernel@xxxxxxxxxx> > >> wrote: > >> > What we still need, though, is an open source version of > >> > wmiofck.exe. I am unaware of anything like that existing and > >> > installing the Windows Driver Kit just to run one command which > >> > spits out a single *.h file is not something I would describe as > >> > convenient (been there). > >> > >> I haven't tried to see whether they do what's needed, but there's > >> OpenWBEM and OpenPegasus. > >> > >> Anyway, if such a tool exists, it would be handy to expose the binary > >> MOF data to userspace so the tool could be used to help get WMI > >> working on new platforms. > > > > In this case, when WMI stay in kernel, MOF data could be exported via > > debugfs? I think there is no need to have them in sysfs stable ABI. As > > above usage (get WMI working on new platforms) looks like for debugging > > purpose. > > > > That's a reasonable point. > Also agreed. -- Darren Hart VMware Open Source Technology Center
