Here comes the next version of WMI. Patch 1 (Add driver and in kernel interface): IMNSHO, this patch is ready for testing . Ideally, I'd like to see it go up to -mm and start crash^^^^^working on other systems. (Of course, outside review is always appreciated - reviewing my own patches is getting a tad boring). (As a mild aside - the driver is currently available on all ACPI enabled architectures. However, if there are no ia64 systems with WMI ACPI devices, then we could later limit the driver to just x86). Patch 2 (Add sysfs userspace interface): This patch is the one that really needs another pair of eyes looking over it. It _works_, but I'm not sure if it's the best way to expose WMI ACPI to userspace. In particular, I'm not sure now about creating kobjects for all the instances of each GUID, then having separate variables and data pointers for each instance; the alternative would be to add more sysfs files under each GUID kobject to handle the instance to call, in a similar way to how method_id is specified to methods. However, that starts making data queries/ writes more complicated, let alone method calls. -Carlos -- E-Mail: carlos@xxxxxxxxxxxxxxxxxxx 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
