On Mon, 19 Mar 2007 21:12:40 -0300 Henrique de Moraes Holschuh <hmh@xxxxxxxxxx> wrote: > On Mon, 19 Mar 2007, Kristen Carlson Accardi wrote: > > Is this what you had in mind? (Warning - I didn't test this). > > > > > > Allow the driver to be loaded with an option that will allow userspace to > > control whether the laptop is ejected immediately when the user presses the > > button, or only when the syfs undock file is written. > > > > if immediate_undock == 1, then when the user presses the undock button, the > > laptop will send an event to userspace to notify userspace of the undock, but > > then immediately undock without waiting for userspace. This is the current > > behavior, and I set this to be the default. > > > > if immediate_undock == 0, then when the user presses the undock button, the > > laptop will send an event to userspace and do nothing. User space can query > > the "flags" sysfs entry to determine if an undock request has been made by > > the user (if bit 1 is set). User space will then need to write the undock > > sysfs entry to complete the undocking process. > > Yes, that's it exactly. I didn't try to test it, as I don't have a dock, > but the above describes what I wanted, indeed. > Ok - I will implement this for real later this week and try to get something that is somewhat tested by friday. I won't have access to my test laptops till later in the week. - 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
