> > By default the kernel will act when the rfkill button is pressed, it will loop > > through all registered buttons of the same type and change the state. > > Userspace can read the "state" sysfs file to see the current status, > > but if a userspace tools wants to take control of taking action when the button is pressed, > > or at least doesn't want the kernel to do anything, 1 should be written to "claim" to > > tell the kernel that it should back off and ignore all events. > > ok thx for explaining this will talk to the nm and hal people about it > and see how they want things to work than I will create patches to > implement it. > which drivers support it now? rt2x00 and ?? or are they the only ones right now? In wireless-dev it is currently only rt2x00, But I have heard about work in progress for: wistron_btns thinkpad_acpi MSI S270 I am however not sure about their status. Ivo - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
