On Tuesday 30 October 2007 14:28:10 Carlos Corbacho wrote: > There are also other technical problems with this, beyond my own personal > disagreement - since WMI relies so heavily on ACPI (well, the driver here > is really just a simple wrapper), then you would have to start exporting > bits of ACPI to userspace to access WMI. As mentioned in the original > patches - the mapper knows nothing about "types", this knowledge is known > only by the caller - WMI just deals in acpi_buffer. My understanding is > that ACPI would have to export the required functions and data structures > so that userspace could provide then translate from acpi_buffer to the > known type (unless there is another way round this to import and export the > data to/ from userspace?) To backtrack slightly - I'm wrong on this point; after sleeping on this for the night (and/ or application of cluebat), I can modify the functions to let userspace call them without exporting half of ACPI in the process. However, I still believe that HAL is the wrong application to deal with WMI. -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
