On Mon, Jul 05, 2010 at 04:49:45PM -0300, Henrique de Moraes Holschuh wrote: > On Mon, 05 Jul 2010, Zhang Rui wrote: > > > I think if you can listen to uevents you can just as easily open /dev/ > > > input/eventX and listen to proper input events. > > > > > the question is users may want to get the lid switch STATUS, > > asynchronously. > > More often than not, you need to know the current state when dealing > with EV_SW, to be able to do anything sensbile with it in GUIs, etc. > I understand the need of getting the current state of a lid switch/key/etc (and for that someone just need to write a utility useable from shell scripts). But I do not understand how adding switch state to uevents (that are emitted normally only when a new device is created) will help here. -- Dmitry -- 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
