On Wed, Jan 16, 2008 at 01:38:35AM +0000, Carlos Corbacho wrote: > The question is, would exporting the GUID virtual device and using that as > the > parent make more sense? So, in the case of hp-wmi, it only uses the GUID > 95F24279-4D7B-4334-9387-ACCDC67EF61C, so should we use the virtual device > associated with that GUID as the parent, or just have WMI itself as the > parent device? I'm really not sure which would be the better way to go.
It's possible for a driver to bind itself to multiple GUIDs, and I guess it's /potentially/ possible for a machine to have multiple event GUIDs. I'm not sure whether those should be created as separate input devices, or whether it would make sense for a driver to bind them into a single input driver. If the latter, wmi probably ought to be the parent? -- Matthew Garrett | [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
