On Mon, 12 Jan 2009, Hans Henry von Tresckow wrote: > As an interested User/lurker, it seems that allowing rfkill to power > down as much of the device as possible in the "killed" state would be > desirable. This would help extend battery life when wifi is not > needed. It seems reasonable to assume that the interface would need > reconfiguring once the rfkill switch is turned back on. Agreed, but the real question is not that. It is "who is responsible for restoring the interface state, and to what extent"? If you kick it out of the bus (cause a full hotunplug on rfkill block, and a hotplug when rfkill unblocks), it is userspace. But what if you do it halfway? That's what is being asked here... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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
