On Tuesday 01 August 2017 13:19:16 Andy Lutomirski wrote: > On Tue, Aug 1, 2017 at 1:03 PM, Darren Hart <dvhart@xxxxxxxxxxxxx> wrote: > > On Tue, Aug 01, 2017 at 08:37:28AM -0700, Andy Lutomirski wrote: > >> This adds a sysfs binary attribute 'wdg' on the bus device > >> (i.e. /sys/class/wmi_bus/wmi_bus-*/wdg) that contains the raw _WDG > >> data from ACPI. This can be used along with the wmi-bmof driver to > >> decode the raw interface data from ACPI. > > > > I don't recall seeing mention of this is the documentation I read as a > > requirement to decoding the interface with the bmof. Do Windows systems export > > _WDG to userspace? > > > > Why do we need to export _WDG? > > This was a feature that Pali asked for. Pali, since you seem to be > working on userspace tooling, can you explain exactly what you'd use > it for? Take raw BMOF and WDG buffers from ACPI and parse them in userspace. Then provide needed information like mapping from MOF event name to ACPI event name based on info from WDG buffer. Ideally ability to create dump of BMOF and WDG on one computer and then parse those data on another. Having original BMOF and WDG structures is a good for debugging and development purpose. > On my laptop, at the very least, it would allow user code to determine > that there's a WMI GUID that doesn't show up in sysfs. It doesn't > show up in sysfs because the ACPI methods are completely missing, but > it's still there in WDG. This prints a warning when wmi.ko is loaded, > but maybe the userspace tooling would care, for debugging if nothing > else. -- Pali Rohár pali.rohar@xxxxxxxxx
