On Fri, 2008-08-29 at 17:05 +0200, Thomas Renninger wrote: > Subject was: > Re: [PATCH 4/5] ACPI: WMI: Add sysfs userspace interface > > On Wednesday 27 August 2008 22:44:49 Matthew Garrett wrote: > > On Wed, Aug 27, 2008 at 09:21:54PM +0100, Carlos Corbacho wrote: > > > Can we abuse uevent and cram all the GUID's into just one MODALIAS line? How many id's of what size do we have? What would be the maximum string length? > > Looking at the udev rules, I suspect we need one event per GUID. > > > > > Alternatively, maybe just have the directories numbered 1 to X, and have > > > a uevent file under each, since we don't care about trying to abuse sysfs > > > to let userspace talk to WMI anymore. A "uevent" file? That file is mechanic of the driver-core and created automatically for every device. It has well defined behaviour, like you can trigger a uevent action, or read the event environment. Custom subdirs with custom "uevent" files would not do anything, I guess. You would need a "struct device" for every directory and uevent file. What do you have in mind? Care to paste-in some example strings? > > Yeah, that'd work for me. > > You should add Kay if you get stuck... > Based on Kay's recent description on the linux-acpi list I set up > this documentation. IMO it's worth adding, Andi, Kay? Oh, that sounds a bit too much like "talking". I guess, it should be rewritten, before it goes into the Documentation directory. :) Thanks, Kay -- 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
