On Fri, 2008-07-04 at 16:55 -0300, Henrique de Moraes Holschuh wrote: > On Wed, 02 Jul 2008, Dan Williams wrote: > > That would be more useful than the current enum, yes. > > Dan, you do have a strong user case for "just software rfkilled", "just > hardware rfkilled" and "soft+hard rfkilled" as opposed to simply "software > rfkilled" and "hardware rfkilled, maybe software rfkilled as well" ? No, I don't have a _NetworkManager_ usecase for being able to distinguish between HW and HW+SW. Just an observation that stuff other than NM might want to figure that out for UI or something. But if the HW block is on, NM doesn't care about softblock because you can't use the radio anyway. If the HW switch is unblocked, NM will un-SW-block the radio anyway, since HW-unblock is definitely a user-initiated option and signals user intent to unblock the radio irregardless of SW block state from something else. Dan -- 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
