On Wednesday 31 October 2007 12:21:10 Carlos Corbacho wrote: > On Wednesday 31 October 2007 00:18:19 Carlos Corbacho wrote: > > On Tuesday 30 October 2007 22:52:30 Carlos Corbacho wrote: > > > On Tuesday 30 October 2007 18:18:22 Len Brown wrote: > > > > 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. > > > > > > The main problem to overcome with a sysfs interface is that a > > > WMI-ACPI call takes multiple values. > > > > So, thinking this over more carefully, whilst sysfs can probably be used > > to export data, I'm not entirely convinced for using it to input > > arbitrary data types, unless there's some way we can get round this? > > After sleeping on the matter, I'm now certain that sysfs is the wrong way > to go for allowing userspace to access WMI-ACPI - we're trying to pass and > return too much data for sysfs to handle. On second thoughts, my other proposal won't work either - we'd end up with a mess of either ioctl's or sysctl's to call from userspace (I really should read up on my userspace interaction a bit more). The sysfs proposal could be made to work, it will just be a little cumbersome (I'll have a go at implementing it and see how it works out). -Carlos -- E-Mail: cathectic@xxxxxxxxx Web: strangeworlds.co.uk GPG Key ID: 0x23EE722D - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
