On Mon, May 15, 2006 at 05:12:20PM +0200, Ivo van Doorn wrote: > Well I would think it is cleaner to inform userspace that the button is > pressed > and let userspace sort out what exactly should happen. > But I doubt it will be a good idea when the driver is sending and event _and_ > disabled the radio. It could be that the user wants something to be done > before the radio is being disabled.
Some hardware designs disable the radio in hardware, some don't.. In other words, the behavior would not be consistent between hardware designs unless the radio would be disabled unconditionally in software-processed case. I would like to be able to trust on the rfkill to really kill the radio regardless of whether the user space mechanism is in place or not, i.e., I see this as a function that can be used to disable radio in environments were use of wireless devices is not allowed for some reason. Sending an event to user space would be a good additional indication that the radio was disabled. If user space wants to do something first, I would think that doing this with full software control (i.e., not depending on any particular hardware button and just having a UI mechanism for triggering this) would allow more consistent behavior. -- Jouni Malinen PGP id EFC895FA - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
