On Mon, Mar 06, 2006 at 07:58:03PM +0100, Jiri Benc wrote: > The problem with this flag is that it is set from > ieee80211_init_client() function, which is removed in next patch and it > isn't clear when it should be set to 1. By trying to figure this out, I > realized that it is completely unused. > > Ok, it is probably useful. Let's rename it to something more obvious > (RADIO_ENABLED? ADM_RFKILL?). But I think it shouldn't be re-enabled by > the kernel automatically when station interface is added/brought up. > Does this sound reasonable?
I agree completely with renaming it. I did not implement that part and haven't really ever liked the name.. ;-) Both of the proposed alternatives sound acceptable. Radio was enabled for station modes automatically to make it easier for users. hostapd is taking care of that for AP modes, but for client mode, there was no automatic mechanism. In other words, it may be useful to enable the radio automatically in some cases (e.g., if hostapd/wpa_supplicant is not doing this for the user). -- 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
